# Reloading config from another service in docker-compose stack

**URL:** <https://discourse.haproxy.org/t/reloading-config-from-another-service-in-docker-compose-stack/9859>\
**Category:** Help!\
**Created:** [May 23, 2024, 2:26pm UTC](https://discourse.haproxy.org/t/reloading-config-from-another-service-in-docker-compose-stack/9859 "2024-05-23T14:26:19Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![victornor](https://avatars.discourse-cdn.com/v4/letter/v/6bbea6/32.png) [@victornor](https://discourse.haproxy.org/u/victornor)\
**Post date:** [May 23, 2024, 2:26pm UTC](https://discourse.haproxy.org/t/reloading-config-from-another-service-in-docker-compose-stack/9859/1 "2024-05-23T14:26:19Z")

</div>

I’m trying to figure out how i can signal the haproxy-ubuntu service to reload configuration from another service in my docker-compose stack.

I see a general solution being to mount the docker.sock and sending a docker SIGHUP signal to a specific image name. But depending on where i run my docker-compose, the service image names will be different.

Another option would be to have the ability to signal a config reload through the dataplane api, which currently seems to only be an option when doing an updating call?

---

<div class="post-metadata">

**Author:** ![wlallemand](https://avatars.discourse-cdn.com/v4/letter/w/bc8723/32.png) [@wlallemand](https://discourse.haproxy.org/u/wlallemand)\
**Post date:** [June 4, 2024, 8:50am UTC](https://discourse.haproxy.org/t/reloading-config-from-another-service-in-docker-compose-stack/9859/2 "2024-06-04T08:50:23Z")

</div>

You could probably share a master CLI in a mounted volume between the 2 containers and send a “reload” to this socket.

[http://docs.haproxy.org/3.0/management.html#9.4.1-reload](http://docs.haproxy.org/3.0/management.html#9.4.1-reload)