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

Remote containers not working on Mac OS #3149

Closed
vrmerlin opened this issue Jun 8, 2020 · 8 comments
Closed

Remote containers not working on Mac OS #3149

vrmerlin opened this issue Jun 8, 2020 · 8 comments
Assignees
Labels
containers Issue in vscode-remote containers info-needed Issue requires more information from poster

Comments

@vrmerlin
Copy link

vrmerlin commented Jun 8, 2020

  • VSCode Version: 1.45.1
  • Local OS Version: macOS Mojave 10.14.6
  • Remote Extension/Connection Type: Docker
  • Docker Desktop for macOS: 2.3.0.3

Steps to Reproduce:

  1. Installed Docker Desktop, and insured i can successfully run containers from the command line and VSC, without problem.
  2. Installed Remote Containers 0.117.1
  3. Selected "Remote-Containers: Try a Sample..."
  4. Selected the Java sample

When I do this, the workspace resets, and pops up a dialog box that says "The 'docker' command was not found. Make sure Docker is installed". Also in the terminal, I see the following:

[0 ms] Start: Resolving remote
[3 ms] Start: Check Docker is running
[3 ms] Start: Run: docker info
[9 ms] Docker returned an error code ENOENT, message: spawn docker ENOENT

I'm running all the "latest and greatest", and Docker is working just fine from the command line. Also, the Docker extension in VSC is working fine too (I can start/stop docker-compose.yml, inspect containers and container logs, etc, from within VSC).

Any ideas what might wrong with my configuration?

@github-actions github-actions bot added the containers Issue in vscode-remote containers label Jun 9, 2020
@chrmarti
Copy link
Contributor

Try starting VS Code from the terminal, maybe the updated PATH has not been picked up by the dock?

@chrmarti chrmarti self-assigned this Jun 15, 2020
@chrmarti chrmarti added the info-needed Issue requires more information from poster label Jun 15, 2020
@vrmerlin
Copy link
Author

No, i tried that and the same problem occurred.

@chrmarti
Copy link
Contributor

What do you get for which -a docker in the terminal?

@vrmerlin
Copy link
Author

When i do which -a docker I get back /usr/local/bin/docker

@chrmarti
Copy link
Contributor

Try setting /usr/local/bin/docker as the value for the Docker CLI path setting. Does that help?
image

@sat0yu
Copy link

sat0yu commented Jul 3, 2020

I've run into the same error and resolved with @chrmarti 's suggestion #3149 (comment)

@github-actions
Copy link

Hey @chrmarti, this issue might need further attention.

@vrmerlin, you can help us out by closing this issue if the problem no longer exists, or adding more information.

@chrmarti
Copy link
Contributor

chrmarti commented Nov 2, 2020

Closing this as we haven't heard back from OP.

@chrmarti chrmarti closed this as completed Nov 2, 2020
@github-actions github-actions bot locked and limited conversation to collaborators Dec 17, 2020
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
containers Issue in vscode-remote containers info-needed Issue requires more information from poster
Projects
None yet
Development

No branches or pull requests

3 participants