{"action":"opened","issue":{"url":"https://api.github.com/repos/gliderlabs/registrator/issues/248","labels_url":"https://api.github.com/repos/gliderlabs/registrator/issues/248/labels{/name}","comments_url":"https://api.github.com/repos/gliderlabs/registrator/issues/248/comments","events_url":"https://api.github.com/repos/gliderlabs/registrator/issues/248/events","html_url":"https://github.com/gliderlabs/registrator/issues/248","id":106433903,"number":248,"title":"Don't deregister on SIGHUP","user":{"login":"activeshadow","id":9335331,"avatar_url":"https://avatars.githubusercontent.com/u/9335331?v=3","gravatar_id":"","url":"https://api.github.com/users/activeshadow","html_url":"https://github.com/activeshadow","followers_url":"https://api.github.com/users/activeshadow/followers","following_url":"https://api.github.com/users/activeshadow/following{/other_user}","gists_url":"https://api.github.com/users/activeshadow/gists{/gist_id}","starred_url":"https://api.github.com/users/activeshadow/starred{/owner}{/repo}","subscriptions_url":"https://api.github.com/users/activeshadow/subscriptions","organizations_url":"https://api.github.com/users/activeshadow/orgs","repos_url":"https://api.github.com/users/activeshadow/repos","events_url":"https://api.github.com/users/activeshadow/events{/privacy}","received_events_url":"https://api.github.com/users/activeshadow/received_events","type":"User","site_admin":false},"labels":[],"state":"open","locked":false,"assignee":null,"milestone":null,"comments":0,"created_at":"2015-09-14T21:41:39Z","updated_at":"2015-09-14T21:41:39Z","closed_at":null,"body":"When a SIGHUP is sent to a container (ie. using something like `docker kill -s HUP container-ID`), the container is deregistered, but never reregistered, even though the container is still running.\r\n\r\nMy use case is with Nginx and docker-gen running in separate containers. I'm using an Nginx container to proxy requests to one or more API servers running in containers, and I'm using docker-gen to monitor for new API server containers in order to update and reload (via SIGHUP) the Nginx config. See [here](https://github.com/jwilder/docker-gen#separate-container-install) for more details regarding this use case.\r\n\r\nI'm using registrator to make my Nginx proxy container available via my Consul-based DNS server, and find that when new API server containers are added the DNS entry for the Nginx proxy goes away. I can restart the Nginx proxy via `docker restart` and it shows back up again.\r\n\r\nI suppose the feature requested in #128 could be a fix for this, but am wondering if the SIGHUP event can be handled directly instead."}}