{"action":"created","issue":{"url":"https://api.github.com/repos/docker/docker/issues/9120","labels_url":"https://api.github.com/repos/docker/docker/issues/9120/labels{/name}","comments_url":"https://api.github.com/repos/docker/docker/issues/9120/comments","events_url":"https://api.github.com/repos/docker/docker/issues/9120/events","html_url":"https://github.com/docker/docker/issues/9120","id":48520650,"number":9120,"title":"Add ability to handle registry downtimes via a 503 HTTP error code","user":{"login":"kencochrane","id":261601,"avatar_url":"https://avatars.githubusercontent.com/u/261601?v=3","gravatar_id":"","url":"https://api.github.com/users/kencochrane","html_url":"https://github.com/kencochrane","followers_url":"https://api.github.com/users/kencochrane/followers","following_url":"https://api.github.com/users/kencochrane/following{/other_user}","gists_url":"https://api.github.com/users/kencochrane/gists{/gist_id}","starred_url":"https://api.github.com/users/kencochrane/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/kencochrane/subscriptions","organizations_url":"https://api.github.com/users/kencochrane/orgs","repos_url":"https://api.github.com/users/kencochrane/repos","events_url":"https://api.github.com/users/kencochrane/events{/privacy}","received_events_url":"https://api.github.com/users/kencochrane/received_events","type":"User","site_admin":false},"labels":[{"url":"https://api.github.com/repos/docker/docker/labels//dist/registry","name":"/dist/registry","color":"5319e7"},{"url":"https://api.github.com/repos/docker/docker/labels/Distribution","name":"Distribution","color":"e11d21"},{"url":"https://api.github.com/repos/docker/docker/labels/improvement","name":"improvement","color":"bfe5bf"},{"url":"https://api.github.com/repos/docker/docker/labels/white-belt","name":"white-belt","color":"ffffff"}],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":26,"created_at":"2014-11-12T15:12:30Z","updated_at":"2015-03-11T18:00:07Z","closed_at":null,"body":"Right now if the registry wants to have a scheduled downtime for routine maintenance there isn't a good way to notify someone using the docker engine. Two things we can do to make this better.\r\n\r\n1. Allow some why to display a message to the user ahead of time, letting them know when the maintenance will be, giving them a warning before it happens.\r\n\r\n2. When the registry goes offline, it will start serving 503 HTTP status codes, where ever we interact with the registry API's the engine should be able to handle this case, and display the message that comes back with the response to the user, letting them know what is going on. Right now this just give them an error, with no message and it isn't very helpful.\r\n\r\n1 is less important, but I figured if we are going to talk about this, lets see what the best possible solution would be, and strive for that.\r\n\r\nOpen for other suggestions on how to make this better."},"comment":{"url":"https://api.github.com/repos/docker/docker/issues/comments/78323156","html_url":"https://github.com/docker/docker/issues/9120#issuecomment-78323156","issue_url":"https://api.github.com/repos/docker/docker/issues/9120","id":78323156,"user":{"login":"jfrazelle","id":1445228,"avatar_url":"https://avatars.githubusercontent.com/u/1445228?v=3","gravatar_id":"","url":"https://api.github.com/users/jfrazelle","html_url":"https://github.com/jfrazelle","followers_url":"https://api.github.com/users/jfrazelle/followers","following_url":"https://api.github.com/users/jfrazelle/following{/other_user}","gists_url":"https://api.github.com/users/jfrazelle/gists{/gist_id}","starred_url":"https://api.github.com/users/jfrazelle/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/jfrazelle/subscriptions","organizations_url":"https://api.github.com/users/jfrazelle/orgs","repos_url":"https://api.github.com/users/jfrazelle/repos","events_url":"https://api.github.com/users/jfrazelle/events{/privacy}","received_events_url":"https://api.github.com/users/jfrazelle/received_events","type":"User","site_admin":false},"created_at":"2015-03-11T18:00:07Z","updated_at":"2015-03-11T18:00:07Z","body":"The main issue here is an easy way for hub to depreciate something and send us a message back so if that is through the manifest I guess that is fine but what about v1?"}}