Use port 8080/tcp

[ooonea]

Hi, I have installed watchtower on a Scaleway server. On the server running Ubuntu 16.04.7 with Docker pre-installed. I have three containers loaded: thelounge, nginx and letsencrypt-companion. After installing watchtower , the docker ps command returns this to me: pox.txt
Is it normal for watchtower to use port 8080? In the examples on the internet there is never any port used.

[simskij]

Hi!

You don't have to map that port, but yes - it's normal. It's for the HTTP API mode described here, which we probably need to document better. 😅

[ooonea]

So even if I use the basic command to start watchtower automatically it uses port 8080? However both netdata and lsof tell me that no process is listening on that port. Thanks a lot ❤️

[simskij]

Correct. 👍 This is the reason for what you're seeing, but as you say, unless you enable the HTTP API, nothing will listen on that port anyway.

watchtower/dockerfiles/Dockerfile

Line 17 in c917b15

EXPOSE 8080

[ooonea]

Perfect, you have been very kind and clear.

[dreamflasher]

Is there any way to turn this off?

[dreamflasher]

It seems in the current version it's enabled by default? At least I am running the command from the doc without any env, and in docker ps it shows as listening to 8080.

[piksel]

No, it's just showing what ports are declared in the Dockerfile, that is not something you can toggle at runtime.

[quincarter]

I would like to know how to disable this or change the port. It conflicted with a container I had and affected customers because that port was exposed already for my existing container

[piksel]

@quincarter Unless you forward it, the port is not in use. And IF you forward it, you specify what port you use on the host. The port specification in the Dockerfile doesn't cause any conflict.

[simskij]

Yeah, so when running it, either omit -p 8080:8080 (or whatever you might have, or in the case of docker-compose, don't include a port mapping dict.