You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I've been trying to get ContainerSSH working for a lab environment, but have run into a snag.
When using VSCode (via the 'Remote - SSH' extension), I can get into into a container properly, and everything works fine. However, when you end the connection (by closing vscode or just dropping the ssh connection in vscode), ContainerSSH isn't able to clean up the container. These debug messages are emitted by the daemon:
containerssh-1 | {"timestamp":"2024-09-30T22:04:11Z","level":"debug","code":"DOCKER_EXIT_CODE_FAILED","message":"Failed to fetch exit code, retrying in 1 second (Program still running)","details":{"authenticatedUsername":"","backend":"docker","connectionId":"c0784ed18e3f4ccf8fed9182235ac14e","containerId":"1c3e0d3a479918c49b71237422b1bfaa0d8826cabdc67c95e7d0634cf071149a","module":"backend",...}}
containerssh-1 | {"timestamp":"2024-09-30T22:04:12Z","level":"error","code":"DOCKER_EXIT_CODE_FAILED","message":"Failed to fetch exit code, giving up (Program still running)","details":{"authenticatedUsername":"","backend":"docker","connectionId":"c0784ed18e3f4ccf8fed9182235ac14e","containerId":"1c3e0d3a479918c49b71237422b1bfaa0d8826cabdc67c95e7d0634cf071149a","module":"backend",...}}
(This is using the docker backend, btw) It looks like VSCode is running something that doesn't get gracefully terminated by docker, and ContainerSSH doesn't force the container to drop. They just sit around forever.
I added 10s timeouts (for 'signal' and 'containerStop') via the config server, but no joy. Any ideas on how to force this?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
I've been trying to get ContainerSSH working for a lab environment, but have run into a snag.
When using VSCode (via the 'Remote - SSH' extension), I can get into into a container properly, and everything works fine. However, when you end the connection (by closing vscode or just dropping the ssh connection in vscode), ContainerSSH isn't able to clean up the container. These debug messages are emitted by the daemon:
(This is using the docker backend, btw) It looks like VSCode is running something that doesn't get gracefully terminated by docker, and ContainerSSH doesn't force the container to drop. They just sit around forever.
I added 10s timeouts (for 'signal' and 'containerStop') via the config server, but no joy. Any ideas on how to force this?
Beta Was this translation helpful? Give feedback.
All reactions