)]}'
{"doc/multinode.rst":[{"author":{"_account_id":7488,"name":"Jeffrey Zhang","email":"zhang.lei.fly@gmail.com","username":"Jeffrey4l"},"change_message_id":"e7d739dea76bcae91d1ebd34b8bbe1697377497f","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"::"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"    -e REGISTRY_PROXY_REMOTEURL\u003dhttps://registry-1.docker.io \\"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"After starting the registry, it is necessary to instruct Docker that it will"},{"line_number":33,"context_line":"be communicating with an insecure registry. To enable insecure registry"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da4df55a_c9628c16","line":30,"updated":"2016-12-22 02:46:55.000000000","message":"need add --registry-mirror\u003d\u003cprivate-registry\u003e:\u003cport\u003e\n\nAnd this is a little out of kolla\u0027s doc. how about simple add a link to https://docs.docker.com/registry/recipes/mirror/","commit_id":"6c15459c87eddf7e1ec49f3381e7558989407263"},{"author":{"_account_id":7488,"name":"Jeffrey Zhang","email":"zhang.lei.fly@gmail.com","username":"Jeffrey4l"},"change_message_id":"a7ea6f8434fc79702855520d47b917ae446b7ff7","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"::"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"    -e REGISTRY_PROXY_REMOTEURL\u003dhttps://registry-1.docker.io \\"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"After starting the registry, it is necessary to instruct Docker that it will"},{"line_number":33,"context_line":"be communicating with an insecure registry. To enable insecure registry"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da4df55a_a31e0e61","line":30,"in_reply_to":"da4df55a_6a35f244","updated":"2016-12-23 05:04:26.000000000","message":"Base on the official doc, when we configured proxy_remoteurl for docker registry, you need add `--registry-mirror` to you docker-engine. otherwise, it is useless.\n\ncould u explain this? i do not think simple add `proxy_remoteurl` works as your expect.\n\nhttps://docs.docker.com/registry/recipes/mirror/#/configuring-the-docker-daemon","commit_id":"6c15459c87eddf7e1ec49f3381e7558989407263"},{"author":{"_account_id":1390,"name":"Paul Bourke","email":"pauldbourke@proton.me","username":"pauldbourke"},"change_message_id":"4129505fe344e4111599ebc6c4802bca5ffed0e8","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"::"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"    -e REGISTRY_PROXY_REMOTEURL\u003dhttps://registry-1.docker.io \\"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"After starting the registry, it is necessary to instruct Docker that it will"},{"line_number":33,"context_line":"be communicating with an insecure registry. To enable insecure registry"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da4df55a_bb656ee2","line":30,"in_reply_to":"da4df55a_6a35f244","updated":"2016-12-22 16:44:53.000000000","message":"I\u0027m good with just adding this to start-registry if it makes it more useful and doesn\u0027t seem to affect standard functionality","commit_id":"6c15459c87eddf7e1ec49f3381e7558989407263"},{"author":{"_account_id":22477,"name":"Matt McEuen","email":"matt.mceuen@att.com","username":"mattmceuen"},"change_message_id":"c8307edfbb7ee75681b2e344963f71ac3158a07b","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"::"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"    -e REGISTRY_PROXY_REMOTEURL\u003dhttps://registry-1.docker.io \\"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"After starting the registry, it is necessary to instruct Docker that it will"},{"line_number":33,"context_line":"be communicating with an insecure registry. To enable insecure registry"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da4df55a_e90c14ee","line":30,"in_reply_to":"da4df55a_a31e0e61","updated":"2016-12-28 00:15:15.000000000","message":"Sorry for the delay; I dug into this some more and did a bunch of testing to make sure I\u0027m understanding it right.\n\nREGISTRY_PROXY_REMOTEURL is sufficient to configure the *registry* itself to be a proxy.  The `--registry-mirror`argument, on the other hand, tells the docker daemon (the *client* of the registry) to use the local registry by default when pulling from docker hub.  I.e., \"docker pull kolla/xyz\" would be directed to our local registry mirror.  `--registry-mirror` also a global change for docker on the host (not specific to kolla images).   \n\nWe don\u0027t need that behavior -- we specify the Kolla registry explicitly in globals.yml (via `docker_registry`), resulting in an explicit pull from a specific registry, e.g. \"docker pull 192.168.1.1:5000/kolla/xyz\".  Leaving `--registry-mirror` out also leaves any other non-kolla-related docker pulls on the host unaffected, which seems like a good idea. I\u0027ve tested this and it works as expected.","commit_id":"6c15459c87eddf7e1ec49f3381e7558989407263"},{"author":{"_account_id":22477,"name":"Matt McEuen","email":"matt.mceuen@att.com","username":"mattmceuen"},"change_message_id":"b00967fdda4a44a59536376d807c48cb06165052","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"::"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"    -e REGISTRY_PROXY_REMOTEURL\u003dhttps://registry-1.docker.io \\"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"After starting the registry, it is necessary to instruct Docker that it will"},{"line_number":33,"context_line":"be communicating with an insecure registry. To enable insecure registry"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da4df55a_bef39b09","line":30,"in_reply_to":"da4df55a_bb656ee2","updated":"2016-12-22 17:24:52.000000000","message":"Thanks, Paul.  I can make that change (\u0026 tweak documentation accordingly) -- are you good w/ that path forward too, Jeffrey?","commit_id":"6c15459c87eddf7e1ec49f3381e7558989407263"},{"author":{"_account_id":22477,"name":"Matt McEuen","email":"matt.mceuen@att.com","username":"mattmceuen"},"change_message_id":"19d4d82b96e5a4cfab72f84d530f57dd8c476d94","unresolved":false,"context_lines":[{"line_number":27,"context_line":""},{"line_number":28,"context_line":"::"},{"line_number":29,"context_line":""},{"line_number":30,"context_line":"    -e REGISTRY_PROXY_REMOTEURL\u003dhttps://registry-1.docker.io \\"},{"line_number":31,"context_line":""},{"line_number":32,"context_line":"After starting the registry, it is necessary to instruct Docker that it will"},{"line_number":33,"context_line":"be communicating with an insecure registry. To enable insecure registry"}],"source_content_type":"text/x-rst","patch_set":4,"id":"da4df55a_6a35f244","line":30,"in_reply_to":"da4df55a_c9628c16","updated":"2016-12-22 15:53:18.000000000","message":"Thanks, Jeffrey.  The way I read this, these two parameters do different things:\n\nIf I have four nodes, and start docker on each of them with --registry-mirror, then each of the four nodes will have a specific-purpose local caching registry (four of them total)\n\nIf I have four nodes, and explicitly start a registry service on one of them with REGISTRY_PROXY_REMOTEURL, then I\u0027ll have exactly one general-purpose caching registry in my cluster, and it will be general purpose (I can push custom built images as well, and use them in my cluster).\n\nPlease let me know if I\u0027m misunderstanding their use!  I\u0027m using REGISTRY_PROXY_REMOTEURL alone in my cluster and it works well.\n\nAlso, I\u0027m thinking that using a caching registry might be the most common use case we\u0027d want to promote \"in real life\", since multinode will be the norm (so a local registry is important, don\u0027t want to pull redundant ) and we don\u0027t want to force folks to build images if they don\u0027t need to (so caching docker hub is important) -- that\u0027s why I wanted to speak to it in the multinode guide.  Interested in your thoughts.  Thanks!","commit_id":"6c15459c87eddf7e1ec49f3381e7558989407263"}]}