I’ve been testing a lot of images lately and this is a problem I’ve run into enough that I’m starting to think I’m doing something wrong. About 50% of the time when I’m testing an image, port forwarding works exactly as I expect it to, but the other 50% of the time I get the behavior described belo…

[image] typoknig: What is going on here? A lack of understand :slight_smile: Let’s sort this out: User defined networks provide dns-based service discovery. Every bridge network created on the command line or through docker compose is a user defined network. For container to container comm…

In other words, port mapping is not mapping a port from an IP address to the same IP address. You tried to use the container IP for both ports, but there is nothing listening on port 1234 in the container. You made that port available on the host. Using that port on the container’s ip address this w…

I think I’m still missing something. The important bit of my Nginx network config follows this formula for all accessing all containers: proxy_pass http://$container_name:$container_port$request_uri In this case that is: proxy_pass http://xwiki:1234$request_uri Seems like this is what you descri…

[image] typoknig: proxy_pass http://xwiki:1234$request_uri Seems like this is what you described already? If your reverse proxy is running as a native process on the host, and the hostname of the docker host happens to be xwiki, then this would be #3 of my previous post. Note: if the revers…

@meyay Is your server that runs the configuration with the proxy_pass setting in another container besides xwiki or xwiki_db? I would think that if you want to set the proxy_pass and the server that you configured to do that is on the same network, then you would use: proxy_pass http://xwiki:8080$…

Is your server that runs the configuration with the proxy_pass setting in another container besides xwiki or xwiki_db? Yes, my reverse proxy is in its own container. I would think that if you want to set the proxy_pass and the server that you configured to do that is on the same network, then y…

I understand what I was missing now. The way I was thinking I could pick an arbitrary port for a service to listen on is incorrect. A service listens on the port it was made to listen on, and unless there is some configuration mechanism for that service to change its listen port like Transmission …

I’m operating under the assumption that when I start a container, I can specify an arbitrary port for its service to listen on. This is correct, you can specify any port that is not in use for the service to listen on, this is the container port. You can also choose the host port to map to that c…

I see you already solved everything :slight_smile: Just some additional notes: [image] typoknig: I created user defined Docker network because when when I was reading about the default network vs user defined networks it seemed that user defined networks were more performant and I think there w…

Containers not honoring Docker Compose port assignments

General

meyay (Metin Y.) March 9, 2024, 6:27pm 11

If you use nginx and create your own configuration, you might want to read about nginx dns caching, as it provides the solution for how to work around nginx’s dns caching issue.

Topic		Replies	Views
Docker-Compose with nginx on different port General	13	42700	July 6, 2024
In Compose ports do not work Compose	8	18669	May 24, 2023
How to configure docker networking with docker-compose to enable remote access to docker container via IP? General docker	15	53447	July 29, 2020
Docker exposed ports are not accessible from all remote networks Compose docker , docker-compose	14	2681	May 4, 2025
Container can't connect to another container on same host using external DNS or host IP Compose dns , docker	13	20200	September 19, 2023

Containers not honoring Docker Compose port assignments

Related topics