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

Release 0.7.1 #416

Closed
aaron-prindle opened this issue Jul 27, 2016 · 4 comments · Fixed by #5351
Closed

Release 0.7.1 #416

aaron-prindle opened this issue Jul 27, 2016 · 4 comments · Fixed by #5351
Assignees

Comments

@aaron-prindle
Copy link
Contributor

No description provided.

@shouhong
Copy link

There is a change for v0.7.1 "Added a insecure-registry flag to minikube start to support insecure docker registries.". Can you please give an example of how to use this "insecure-registry" flag?

@aaron-prindle
Copy link
Contributor Author

aaron-prindle commented Jul 29, 2016

The --insecure-registry flag is passed through minikube to the libmachine api when provisioning the VM. It should act exactly as docker-machine's --engine-insecure-registry.
An example use of the flag would be:
minikube start --insecure-registry [url-to-insecure-registry]
minikube start --insecure-registry registry.myco.com

@dlorenc
Copy link
Contributor

dlorenc commented Jul 29, 2016

This is out, right?

@aaron-prindle
Copy link
Contributor Author

aaron-prindle commented Jul 29, 2016

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

Successfully merging a pull request may close this issue.

3 participants