Skip to content
This repository has been archived by the owner on Sep 26, 2021. It is now read-only.

Usage of ~/.docker/machine/machines/myvm/config.json file and insecure-registry configuration #491

Open
vberruchon opened this issue May 4, 2016 · 5 comments

Comments

@vberruchon
Copy link

Hi,
where could I find details about using the ~/.docker/machine/machines/myvm/config.json file.
I modifiying this dile to add an insecure-registry but it does nothing even if I do stop with docker-machin, modify the file and start again the boot2docker VM.
I have to edit directly the /var/lib/boot2docker/profile file to add my registries.
But sometime the profile file was regenerated when I start the VM and I had to do it again.

How to use this file config.json?
Is it only used at the creation of the VM? Or should it be at each start? Or is there another command that could help?
Thank you for your help
(I did test today with Toolbox 1.11.1 on Windows - but was)

@vshlapakov
Copy link

@vberruchon I had the same question, you should re-provision your machine after changing the config with docker-machine provision default (found it here).

@vberruchon
Copy link
Author

vberruchon commented Jun 2, 2016

Thanks @vshlapakov, it will probably work with Docker 1.11.
My problem now is that finally I'm back to Docker 1.9.1 and the docker-machine version that came with the Toolbox is 0.5.6 and doesn't support this "provision" command :(
I'm stucked with that version for the moment because of internal platform constraints... perhaps we could package a new Docker-machine version with older docker 1.9.1 but I'm not sure we want to promote Toolbox for large development teams if we have to do this kind of things.

@bbodenmiller
Copy link
Contributor

Can confirm that in 1.12.1 setting the following in config.json works:

            "InsecureRegistry": [
                "registry.company.com"
            ],

then run docker-machine provision default

@jannis-baratheon
Copy link

This should definitely be in the documentation: https://docs.docker.com/registry/insecure/

@speller
Copy link

speller commented Mar 19, 2018

I just fall into this issue and had to spend few hour googling what's the problem. The @bbodenmiller 's answer must be in the docs. The issue is I've found which config setting I should correct, but I didn't know I need to run command docker-machine provision default

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

No branches or pull requests

5 participants