Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Error: "Docker version 17.12.0 or later required on remote host" when select "Attach Visual Studio Code" #9105

Open
SgtErnestBilko opened this issue Oct 16, 2023 · 5 comments
Labels
containers Issue in vscode-remote containers

Comments

@SgtErnestBilko
Copy link

  • VSCode Version: 1.83.1

  • Local OS Version: MacOS 12.5

  • Remote OS Version: MacOS 12.6.2

  • Remote Extension/Connection Type: Dev Containers v0.315.1 (local) Docker v1.26.1 (remote)

  • Docker desktop for Mac (remote): 4.24.2

  • Logs:

Dev Container log

[515226 ms] Start: Run in Host: docker version --format {{.Server.APIVersion}}
[515232 ms] Host server: Error: spawn docker ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[515236 ms] Host server: (node:42024) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 4)
[515236 ms] spawn docker ENOENT
[515238 ms] CLI host's PATH: /usr/bin:/bin:/usr/sbin:/sbin

Steps to Reproduce:

This has worked since installation (Jan 2023) the error only started yesterday afternoon.

  1. SSH onto remote
  2. Right click docker container (using docker extension) and select "Attach Visual Studio Code"
  3. Error message "Docker version 17.12.0 or later required on remote host"
  4. I have deleted .vscode-server and .vscode-remote-containers and restarted VSCode - same issue
  5. I downgraded to previously working VSCode1.82.2 and Docker desktop 4.16.2 - same issue
@github-actions github-actions bot added the containers Issue in vscode-remote containers label Oct 16, 2023
@SgtErnestBilko
Copy link
Author

Downgraded to Dev Containers v.309 fixed the issue
Happy to help troubleshoot latest version v315 if a developer would like to make ocntact

@lixiaoqin0218
Copy link

the same issue:
[77389 ms] Start: Run in Host: docker version --format {{.Server.APIVersion}}
[77438 ms] Host server: Error: spawn docker ENOENT
at ChildProcess._handle.onexit (node:internal/child_process:283:19)
at onErrorNT (node:internal/child_process:476:16)
at process.processTicksAndRejections (node:internal/process/task_queues:82:21)
[77483 ms] spawn docker ENOENT
[77500 ms] Host server: (node:3896) PromiseRejectionHandledWarning: Promise rejection was handled asynchronously (rejection id: 1)
(Use node --trace-warnings ... to show where the warning was created)
[77798 ms] CLI host's PATH: /usr/local/sbin:/usr/local/bin:/usr/sbin:/usr/bin:/sbin:/bin

downgraded dev containers v.309.0 ,it's not work!
image

@yennhi95zz
Copy link

I am facing the same issue. Downgrading Dev Containers v.0.309 doesn't work for me

@Natielle
Copy link

I am facing the same issue. Downgrading Dev Containers v.0.309, v.0.315 doesn't work for me 😢

@Natielle
Copy link

In my case the docker path was wrong. To resolve, I check my docker path with which docker.

So I press Command + Shift + P -> Dev Containers: Settings -> Find Docker Path configuration -> Paste the result (which is a path) of the which docker command and try use Dev container again

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
containers Issue in vscode-remote containers
Projects
None yet
Development

No branches or pull requests

4 participants