Unable to attach VS Code on remote host's containers and 'Error: Unrecognized Container OS' on remote host. #3425
Replies: 2 comments 1 reply
-
The "Attach VSCode" feature is provided by the Remote - Containers extension. You'd have to file an issue in their repo for the Docker version issue. As for the "Unrecognized container OS" issue, this is coming from our file explorer. We use the container OS provided by the inspection result. If you do |
Beta Was this translation helpful? Give feedback.
-
Hi Brandon, I see. Thank you, I'll file an issue in their repo for the docker version. :) Please see the output of docker inspect: docker inspect 2f4d11ac016a |
Beta Was this translation helpful? Give feedback.
-
Hi All,
I'm trying to connect my laptop to a container instance in a remote linux host using vs code. I connect using the remote ssh extension, then after connecting via remote ssh, I attempt to attach to Visual Studio Code. When I do that, I am prompted to upgrade to docker 17.12.0 in windows, however it seems I'm already using the latest version.
If I select install, the docker desktop gets updated. The docker version on the linux server is Docker version 1.13.1, build 7d71120/1.13.1. While my windows laptop is using Docker Desktop 4.5.0 (74594). Do you know how I could get to 17.12.0?
Also while connected via remote ssh to the remote linux server, I also see there are errors about unrecognized OS when on the docker extension. Is it normal to see this in the docker extension while on a remote server?
I could at least connect via shell but I don't have an IDE in the remote linux server. I could script my code using 'nano' or other editors while on the remote linux server, but I'd like to use VS code on my windows laptop if possible. If you could share a good approach to achieve it, then thatt would be great. Thanks!
Thanks.
Beta Was this translation helpful? Give feedback.
All reactions