-
Hi If I use this parameter to spin up an HTTP endpoint while preserving the auto update mechanism I get the weird situation that the HTTP endpoint isn't started. After running the container like documented in: https://containrrr.dev/watchtower/http-api-mode/ (with debug switch) I get the container logs like so: time="2025-01-08T09:26:17+01:00" level=debug msg="Sleeping for a second to ensure the docker api client has been properly initialized."
time="2025-01-08T09:26:18+01:00" level=debug msg="Making sure everything is sane before starting"
time="2025-01-08T09:26:18+01:00" level=debug msg="Retrieving running, stopped, restarting and exited containers"
time="2025-01-08T09:26:19+01:00" level=debug msg="There are no additional watchtower containers"
time="2025-01-08T09:26:19+01:00" level=debug msg="Watchtower HTTP API skipped."
time="2025-01-08T09:26:19+01:00" level=info msg="Watchtower 1.7.1"
time="2025-01-08T09:26:19+01:00" level=info msg="Using no notifications"
time="2025-01-08T09:26:19+01:00" level=info msg="Checking all containers (except explicitly disabled with label)"
time="2025-01-08T09:26:19+01:00" level=info msg="Scheduling first run: 2025-01-12 03:02:01 +0100 CET"
time="2025-01-08T09:26:19+01:00" level=info msg="Note that the first check will be performed in 89 hours, 35 minutes, 41 seconds" Why? Am I supposed to pass in both switches Edit: Yes, I have to pass in both switches. The documentation isn't clear about that fact. |
Beta Was this translation helpful? Give feedback.
Replies: 1 comment
-
Adding this to mark as an answer: Yes, I have to pass in both switches. The documentation isn't clear about that fact. You need to pass in both switches to start the API and continue with scheduled updates. I came looking for the same answer, but didn't look at this at first because it wasn't marked as an answer. |
Beta Was this translation helpful? Give feedback.
Adding this to mark as an answer: Yes, I have to pass in both switches. The documentation isn't clear about that fact.
You need to pass in both switches to start the API and continue with scheduled updates.
I came looking for the same answer, but didn't look at this at first because it wasn't marked as an answer.