"Connection failure" in Web IDE web terminal when using Docker executor
Update
This issue is related to gitlab-runner#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
Example Project
What is the current bug behavior?
What is the expected correct behavior?
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
Results of GitLab environment info
Expand for output related to GitLab environment info
(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`)
Results of GitLab application Check
Expand for output related to the GitLab application check
(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)