Request to change port inside container

[GFNiko]

As I am using IPVLAN Layer 3 in my docker setup, every microservice gets its own ip address. Therefore I don't need different ports. And docker doesn't support port rebinding in an ipvlan L3. So I want to change the given port 5000 to 80, so I dont have the local dns record of 192.168.10.5:5000 to snip.homelab:5000. Let me change it to 192.168.10.5:80 therefore just http://snip.box please
When I run the docker run command
docker run -d --network=home_lab --ip=192.168.10.5 --name=snippetbox --restart=always -v ~/docker/config:/config pawelmak/snippet-box:latest it binds it to the port 5000, even I put --bind :80 or -p 80:80 to the command. How do I use it without port 5000

[schklom]

Why not use a different port, like -p 80:5000?
This does not seem like a rare edge case where you need container port 80.

[GFNiko]

Becasue docker's IPVLAN ignores ports

[schklom]

Oh, I didn't know that.
Unless the dev fixes this, you could link snippet-box to a reverse-proxy and expose the reverse-proxy's port. A basic nginx config would do.

[codesterd]

I usually just change the EXPOSE port in the Dockerfile and build it.

https://www.mend.io/free-developer-tools/blog/docker-expose-port/

[schklom]

@codesterd I don't think that is enough. The software needs to listen on that port.
Also, you don't need to build the Dockerfile if all you change is EXPOSE, this can be changed in your docker-compose.yml or docker run command.

[blakeusblade]

Along the same lines... While defining ports in your docker composer file ie below...

version: '3' services: snippet-box: image: pawelmalak/snippet-box:latest container_name: snippetbox volumes: - /volume1/docker/snippetbox:/app/data ports: - 5212:5813 restart: unless-stopped

The ports gets mapped when defining the ports in the composer file

The result doesn't change whats running inside the container as shown by the logs

[2024-09-04 05:46:16.021 UTC+0] [INFO] server: Server is working on port 5000 in production mode

In most Synology NAS's, this is very bad because Synology's default port is 5000 and when anything uses that port by default regardless of networking, Synology's have issues...

It would be good to have an environmental variable to be able to define the port that the container will run on.