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 is not working proparly after starting dvm #47

Open
odedpriva opened this issue Oct 19, 2014 · 2 comments
Open

docker is not working proparly after starting dvm #47

odedpriva opened this issue Oct 19, 2014 · 2 comments

Comments

@odedpriva
Copy link

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
Copy link

It's the new docker TLS default, see boot2docker/boot2docker#571 and boot2docker/boot2docker#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
Copy link

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"'

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

No branches or pull requests

3 participants