Join Log in
Score:0
avatar Server

Access other Docker containers from loadbalancer container using host network

cn flag
user1933738

For performance and usability (=dynamically reconfigure haproxy front- and backends on the fly without having to modify the systemd unit file that launches the container) I have a haproxy:2.5 container running using --net host that does SSL termination and load balancing.

Now, I want to access other containers on the host (e.g. a nginx container) from inside the haproxy container... but that doesn't work. Since we're running in the host network, the haproxy container uses the /etc/hosts from the host container (obviously) and so "nginx" does not resolve to anything.

I tried creating a separate network local-services which I can attach to the application containers, but attaching it to the haproxy container yields this error:

container sharing network namespace with another container or host cannot be connected to any other network

Is there any other way I can get both dynamic frontend ports in haproxy and connecting to application containers from inside haproxy, other than using e.g. -p 10.0.10.1:8080:80 on the container and 10.0.10.1:8080 in the haproxy backend specification?

34
0 + 0
ธงชาติไทย
Elon Musk
I sit in a Tesla and translated this thread with Ai:

mangohost

Post an answer

Most people don’t grasp that asking a lot of questions unlocks learning and improves interpersonal bonding. In Alison’s studies, for example, though people could accurately recall how many questions had been asked in their conversations, they didn’t intuit the link between questions and liking. Across four studies, in which participants were engaged in conversations themselves or read transcripts of others’ conversations, people tended not to realize that question asking would influence—or had influenced—the level of amity between the conversationalists.