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

DOCKER_HOST not used for viewing containers #2142

Closed
marcpawl opened this issue Jan 9, 2020 · 5 comments
Closed

DOCKER_HOST not used for viewing containers #2142

marcpawl opened this issue Jan 9, 2020 · 5 comments
Assignees
Labels
containers Issue in vscode-remote containers feature-request Request for new features or functionality upstream Issue identified as 'upstream' component related (exists outside of VS Code Remote)

Comments

@marcpawl
Copy link

marcpawl commented Jan 9, 2020

Version: 1.42.0-insider
Commit: cba31b819ea99836daf51cee56299348e9c6d20b
Date: 2020-01-08T05:35:29.477Z
Electron: 6.1.6
Chrome: 76.0.3809.146
Node.js: 12.4.0
V8: 7.6.303.31-electron.0
OS: Darwin x64 17.7.0

What I would like to see is some messages that will make the debugging of the install easier. Why is the step not progressing, after a few minutes I would like to see an error message giving clues.
e.g. Unable to connect to docker port, or command docker ps did not return in a timely manner.

Steps to Reproduce:

  1. Create ssh keys and verify that ssh works without password
  2. In .bashrc setup DOCKER_HOST environment variable
    basement:~ marcpawl$ echo $DOCKER_HOST
    ssh://marcpawl@dcrdev
  3. Reboot
  4. docker ps -a
    Connects to remote host and shows 1 active container and 1 exited container.
  5. From bash prompt, start code
  6. Select Remote Explorer
  7. explore "Containers"
    progress scroll keeps going forever, but no results occur
  8. View Terminal
    basement:~ marcpawl$ echo $DOCKER_HOST
    ssh://mpawlowsky@dcrdev
    basement:~ marcpawl$
@ibalajiarun
Copy link

I am running into the same issue as well. I have set the docker.host setting as mentioned here: https://code.visualstudio.com/docs/remote/containers-advanced#_developing-inside-a-container-on-a-remote-docker-host and used a devcontainer.js file. Below is the terminal log I get:

[0 ms] Start: Resolving remote
[2 ms] Setting up container for folder or workspace: /Users/balaji/workplace/devcontainers/sgx-threshsign

[14 ms] Start: Check Docker is running

and its struck here.

@ibalajiarun
Copy link

I have since figured it was a problem with the hostname. I used the host alias from .ssh/config but vscode couldn't resolve it.

@chrmarti
Copy link
Contributor

chrmarti commented Feb 7, 2020

Tracking as upstream: apocas/docker-modem#113

@chrmarti chrmarti added containers Issue in vscode-remote containers feature-request Request for new features or functionality upstream Issue identified as 'upstream' component related (exists outside of VS Code Remote) labels Feb 7, 2020
@chrmarti
Copy link
Contributor

chrmarti commented Feb 7, 2020

@marcpawl You could add the private key to your ssh-agent as a workaround.

@chrmarti
Copy link
Contributor

This should work now that we have moved off Dockerode.

@github-actions github-actions bot locked and limited conversation to collaborators Dec 10, 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 feature-request Request for new features or functionality upstream Issue identified as 'upstream' component related (exists outside of VS Code Remote)
Projects
None yet
Development

No branches or pull requests

4 participants