-
Notifications
You must be signed in to change notification settings - Fork 507
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
Unable to connect to Docker Machine #580
Comments
@eduardonunesp Sorry you're having troubles. So you're trying to connect to Docker Machine? Have you followed the instructions at https://github.com/microsoft/vscode-docker#connecting-to-docker-machine? |
@StephenWeatherford NP, sorry if I sounded rude, actually I have set the |
Same issue on MacOS 10.14 running VSCode 1.30.2 (1.30.2). Is there a ballpark timeframe for the PR on this one? |
Same issue in Windows 10: docker-machine start Went through several iterations of setting the environment variables as per: I'm using docker-machine with a local VM provider (Virtualbox) **Update - more info: |
I tried this setting: "docker.host": "tcp://192.168.99.100:2376",
"docker.importCertificates": {
"useCertificateStore": true,
"certificatePaths": [
"/etc/ssl/certs/ca-certificates",
"/etc/openssl/certs",
"/etc/pki/tls/certs",
"/usr/local/share/certs",
"C:\\Users\\aksha\\.docker\\machine\\machines\\default"
]
} I get an error as (certificates are too big)
and
|
Chiming in with the same issues as above. I've run DOCKER_TLS_VERIFY=1
DOCKER_HOST=tcp://192.168.64.100:2376
DOCKER_CERT_PATH=.../.docker/machine/machines/vm
DOCKER_MACHINE_NAME=vm However, I'm unable to view my containers in my Docker Machine VM on the explorer. Is there a step that I'm missing in the settings? |
Actually, I just happened across this issue microsoft/vscode#69728 and out of curiosity tried launching code from the command line. Looks like this solved the issue, but it's unintuitive. I can see all of my Docker Machine containers and attach VSCode (using Remote Containers and Insiders) |
I would appreciate a fix for this soon, the extension works when i'm not using |
@deepio Did you use Another question: are you changing out the EDIT: |
Reading back, I don't know whether or not docker toolbox is supported. is it possible for you to migrate from toolbox to docker machine instead or is that a non-starter? |
@JDDoesDev I really appreciate your speedy reply. I'm using
Unfortunately I need to run both docker and docker-toolbox, it's not just one or the other. It would have been nice to have vscode integration for all the machines but I believe it might not be possible at this time. Edit: I've also tried with the --no-proxy flag |
@deepio I'm sorry, The output up there looks like something from a .*rc file or similar. What happens when you actually run |
@JDDoesDev what I posted was just the output of |
I found a fix. I've set docker.host like this, and it worked: |
Save my day! Thank you very much! |
Hi all - just merged #998 to support the following VS Code settings:
Feel free to try the latest build from master and let us know if it works for ya! See these instructions: https://aka.ms/azCodeInsiders |
Can't connect to
docker
even settings theDOCKER_HOST
env var and on config file withDOCKER_HOST
(tcp://192.168.99.100:2376
)Does that extension ever worked on
macOS
andWindows
?macOS:
10.14
VSCode:
Version 1.28.2
The text was updated successfully, but these errors were encountered: