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

Support the Docker daemon flag "insecure-registry=[]" #231

Closed
mcoms opened this issue Nov 11, 2014 · 4 comments
Closed

Support the Docker daemon flag "insecure-registry=[]" #231

mcoms opened this issue Nov 11, 2014 · 4 comments

Comments

@mcoms
Copy link

mcoms commented Nov 11, 2014

I'd love to see support for this flag, which allows Docker to pull from named registries which use plain text authentication, or self-signed SSL certificates.

In v1.3.1, the format is: --insecure-registry self-signed-cert-registry.example.com:5000 when starting the Docker daemon.

@mcoms mcoms changed the title Support the Docker daemon flag insecure-registry=[] Support the Docker daemon flag "insecure-registry=[]" Nov 11, 2014
@djdefi
Copy link

djdefi commented Nov 11, 2014

It is possible to do this with the "options" daemon attribute under the node['docker'] namespace.

 "docker": {
   "options": "--insecure-registry self-signed-cert-registry.example.com:5000"
}

@jperville
Copy link
Contributor

Yes, it is possible to do this with node['docker']['options'] but since that attribute is String so it won't play nice with attribute merging (eg. cannot inject the insecure registry via a role and leave the user free to supply its own custom options). I will work on a PR since I need the feature (and also support for the 'registry-mirror' option which works in a similar manner).

@mcoms
Copy link
Author

mcoms commented Nov 12, 2014

Thanks both — I use Docker with custom options for init/restarts, and hit that merge problem. For now I've specified the full line as options. Look forward to switching to insecure-registry when #232 is merged :)

@tduffield
Copy link
Contributor

I'm closing this issue since the PR has been merged and will be released in 0.37.

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

4 participants