Open jmreicha opened 8 years ago
@nextrevision I'm looking at this now. There are about 5 variables needed for adding a registry and I'm not much of a Ruby developer.
I was thinking of having a docker_registry
variable with all the needed variables inside it but am not sure what the best path to take is here or how to get there. Something like this is what I was thinking of exposing in the Vagrantfile:
node.vm.provision :rancher do |rancher|
rancher.docker_registry = “my-registry”, <- Maps to registry name in Rancher API
registry_url: “index.docker.io”,
username: “test”,
password: “test123”,
email: “test@test.com”
end
Any ideas on a good approach to take?
That sounds good, I think the other variables need to have the rancher.
prefix as well. Perhaps we can also support passing in username, password and email as environment variables for a little added security/portability .
Another one I want to look at doing if I get some time.
It would be nice to automatically configure a Docker registry for rancher-server to connect to in order to pull private Docker images after the server component has been provisioned via some sort of configuration. Again, if it doesn't sound doable please close this.