<!--- Please read this! Before opening a new issue, make sure to search for keywords in the issues filtered by the "regression" or "bug" label: - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=regression - https://gitlab.com/gitlab-org/gitlab/issues?label_name%5B%5D=bug and verify the issue you're about to submit isn't a duplicate. ---> ## Update This issue is related to https://gitlab.com/gitlab-org/gitlab-runner/-/issues/3605 and the Runner team will be the ones to implement changes to the docker executor and resolve this timeout. --- ### Summary We recently set up the Interactive Web Terminal feature on our locally-hosted GitLab runners, which are running the latest version of the runner. I've verified that I can click the "Debug" button during a GitLab CI pipeline and open a terminal to the associated runtime environment. However, when I created a .gitlab-webide.yml file in one of my projects and tried to use that with the Web IDE, I get the message "Connection failure" in the web terminal window. But if I open the project's GitLab CI pipelines page, I can see that my "terminal" job is running, and I can even connect to it if I click the "Debug" button. So it seems I simply can't connect using the Web IDE. ### Steps to reproduce <!-- Describe how one can reproduce the issue - this is very important. Please use an ordered list. --> ### Example Project <!-- If possible, please create an example project here on GitLab.com that exhibits the problematic behavior, and link to it here in the bug report. If you are using an older version of GitLab, this will also determine whether the bug is fixed in a more recent version. --> ### What is the current *bug* behavior? <!-- Describe what actually happens. --> ### What is the expected *correct* behavior? <!-- Describe what you should see instead. --> ### Relevant logs and/or screenshots Our .gitlab-webide.yml ``` terminal: image: docker.mimsoftware.com/orion/containers/tox-test-container:2.1 tags: - docker script: sleep 1200 services: - docker:20.10-dind ``` ### Output of checks <!-- If you are reporting a bug on GitLab.com, write: This bug happens on GitLab.com --> #### Results of GitLab environment info <!-- Input any relevant GitLab environment information if needed. --> <details> <summary>Expand for output related to GitLab environment info</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:env:info`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:env:info RAILS_ENV=production`) </pre> </details> #### Results of GitLab application Check <!-- Input any relevant GitLab application check information if needed. --> <details> <summary>Expand for output related to the GitLab application check</summary> <pre> (For installations with omnibus-gitlab package run and paste the output of: `sudo gitlab-rake gitlab:check SANITIZE=true`) (For installations from source run and paste the output of: `sudo -u git -H bundle exec rake gitlab:check RAILS_ENV=production SANITIZE=true`) (we will only investigate if the tests are passing) </pre> </details> ### Possible fixes <!-- If you can, link to the line of code that might be responsible for the problem. -->