Reloading fails in a linked docker container

[tcharlat]

I have some trouble fixing a bug.

I created a docker image and I wish to use http-master as a sub-domain router.
I link the proxy to another docker, the routing is fine, everything is ok.

If I modify the http-master.conf file, the reloading kicks in, seems fine.

Reloading workers due to config change
[1] Reloading config
[1] Listening on port: port 80
[1] Start successful
All workers reloaded, downtime was 8ms

Except that now the proxy is not responding.

Here is a repo with more details and how to reproduce the bug https://github.com/Kallikrein/http-master-issue

[Nowaker]

Hi @Kallikrein, thanks for your report. Unfortunately, we won't have time to work on your problem now, and can't even give you a time frame. If you're able to find the problem and submit a PR, we'll gladly accept it. Thanks.

[tcharlat]

@Nowaker I have been tinkering and added some debug logs to monitor the relaod process in action and couldn't find why the reload fails. I don't have the first clue on a PR so I am giving up.

Restarting a proxy container is highly simplified by the new network pattern of docker that deprecated linking containers, so I deactivated the auto-reload and restart myself when config changes.

I'll keep digging when I can gather enough time and when I will have the necessary understanding I am obviously currently lacking.

Thanks for your hard work and dedication.

[krlicmuhamed]

Hi @Kallikrein, any luck on running http-master as a docker container?