Container not honoring port mapping #7056
Replies: 1 comment
-
There was an error my config which I have corrected. This was not a port mapping issue, but more a misunderstanding on my part. Please disregard. |
Beta Was this translation helpful? Give feedback.
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
-
My compose file. Note that volumes are commented out because I was debugging and going scorched Earth between each run:
I've got multiple subdomains running behind a reverse proxy. In this example I want
wikijs
to respond to port 8080 as the configuration shows, but the container only responds to port 3000. Strangely, with this configuration I can change my reverse proxy from 8080 to 3000 and get wikijs to pull up in a browser, which doesn't seem like it should be possible. Entering into the container and runningcurl localhost:3000
andcurl localhost:8080
confirms that the former responds, and the latter does not.Beta Was this translation helpful? Give feedback.
All reactions