But in my using Code for these days, never succeed even once after restart my docker container.
Does this issue occur when all extensions are disabled?: Yes/No
(Experimental duplicate detection)
Thanks for submitting this issue. Please also check if it is already covered by an existing one, like:
I experience the same behavior on VSCode 1.38.0-insider (macOS 10.14.6):
When restarting a docker container I'm currently attached to with docker-compose restart my-container VSCode will recognize that the container has stopped, but it stays in Attempting to reconnect... state until I either restart VSCode or reload the window (cmd+shift+P > Developer: Reload Window).
This is a limitation of the reconnect logic which is based on the remote state being present in RAM. Restarting the container looses that state. Closing as out-of-scope, thanks.
Most helpful comment
I experience the same behavior on VSCode 1.38.0-insider (macOS 10.14.6):
When restarting a docker container I'm currently attached to with
docker-compose restart my-containerVSCode will recognize that the container has stopped, but it stays inAttempting to reconnect...state until I either restart VSCode or reload the window (cmd+shift+P > Developer: Reload Window).