Since docker is running within boot2docker containers will be exposed via ports on the boot2docker IP.

Prev All Posts Thoughts Lets chat on Twitter or via Email:).

I suspect this is because there is no varrundocker.sock on the OS X host, and that I would need to use something like.

Itll prevent you from accessing the remote API using basicly like every REST tool you can think about because none of them supports TLS based authentication without quite a lot of configuration.

Once done, you should be able to open:2375info and get some output.

Note that this is as of boot2docker 1.41.

The name of the env variable repalced by the sed command above may change in future.

Maybe theyll even disable TLS by default in future releases.

After all, it appears that recent versions are set up to share volumes from your OS X host rather than the boot2docker vm, which is what youd want most of the time.

But there is no varrundocker.sock path on your OS X host, so what is going on.

When you add a volume to a container under boot2docker it is still sharing whatever is at that path in the vm.

But any paths outside Users will be from the boot2docker vm itself and not your host.

Provide details and share your research But avoid Asking for help, clarification, or responding to other answers.

Making statements based on opinion; back them up with references or personal experience.

Not the answer youre looking for Browse other questions tagged docker boot2docker or ask your own question.

Docker For Mac Vs Boot2Docker