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

Provide instructions for 'docker-in-docker' for docker based planemo machine #26

Open
kellrott opened this issue Feb 23, 2015 · 4 comments

Comments

@kellrott
Copy link
Contributor

Instructions should be added to the deployment of the docker image of the planemo box to instruct the user how to mount the parent OS docker server so the box can deploy sub-containers.

I've used:
--privileged -v /var/run/docker.sock:/var/run/docker.sock

Which mounts in socket to the parent OS's docker server (still need to verify that privileged is necessary)

@jmchilton
Copy link
Member

Yes it should - this command works on Mac OS X?

@kellrott
Copy link
Contributor Author

Weirdly it does. boot2docker only remounts the users home directory into the running VM. So the '/var/run/docker.sock' path that gets posted in isn't from the Mac OS, but rather the VM OS.

@bgruening
Copy link
Member

@kellrott OS-X can never have a /var/run/docker.sock, isn't it?

@kellrott
Copy link
Contributor Author

Yeah, /var/run/docker.sock doesn't exist in MacOS. Boot2Docker's 'shellinit' command sets the DOCKER_HOST environmental variable, which gets used rather then '/var/run/docker.sock'. But if you issue a docker run with '-v /var/run/docker.sock:/var/run/docker.sock' in MacOS, the path gets forwarded into the VM, where it hits a socket that does exist.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

3 participants