search

fnichol / dvm

An on demand Docker virtual machine, thanks to Vagrant and boot2docker. Works great on Macs and other platforms that don't natively support the Docker daemon. Support VirtualBox, VMware, and Parallels.
http://fnichol.github.io/dvm
Apache License 2.0
458 stars 71 forks source link

docker is not working proparly after starting dvm #47

Open odedpriva opened 9 years ago

odedpriva commented 9 years ago

I followed the instruction, added an environment variable of DOCKER_CIDR of 172.18.0.1/16, when trying to use docker from my mac i get the following error: ➜ ~ docker images 2014/10/19 23:26:17 Get https://192.168.42.43:2375/v1.15/images/json: tls: oversized record received with length 20527 ➜ ~ docker pull ubuntu 2014/10/19 23:26:22 Post https://192.168.42.43:2375/v1.15/images/create?fromImage=ubuntu%3Alatest: tls: oversized record received with length 20527

any idea what is causing the error?

dweinstein commented 9 years ago

It's the new docker TLS default, see https://github.com/boot2docker/boot2docker/issues/571 and https://github.com/boot2docker/boot2docker/pull/572. Once this stuff is upstream then you will be able to tweak via an ENV variable, but I suspect there will need to be more plumbing in dvm as well.

CleanCut commented 9 years ago

I worked around this by running this command after I launch boot2docker (In my case, 10.0.0.0/8 represents my entire internal network that I want to allow "insecure" use of images to):

boot2docker ssh 'sudo sh -c "echo \"EXTRA_ARGS=\\\"--insecure-registry 10.0.0.0/8\\\"\" > /var/lib/boot2docker/profile && sudo /etc/init.d/docker restart"'