Clarification on watchtower metrics and API token for a noob #1615
-
|
I am trying to get watchtower api working on my homepage dashboard, but I'm not going to lie. I am very stuck. |
Beta Was this translation helpful? Give feedback.
Replies: 5 comments 17 replies
-
|
i went through literally this exact situation earlier this morning. In fact I did a double take thinking i'd posted your comment under a different name somehow, it was that similar. Anyway, after a lot of digging around and fiddling, I got it working. This is my working compose yaml which just notifies of updates instead of automatically updating them ( version: "2"
services:
app:
image: containrrr/watchtower
hostname: 192.168.1.64
restart: unless-stopped
volumes:
- /var/run/docker.sock:/var/run/docker.sock
ports:
- 8080:8080
environment:
- TZ=Europe/London
- NO_COLOR=true
- WATCHTOWER_SCHEDULE=0 0 19 * * *
- WATCHTOWER_INCLUDE_STOPPED=true
- WATCHTOWER_INCLUDE_RESTARTING=true
- WATCHTOWER_MONITOR_ONLY=true
- WATCHTOWER_HTTP_API_UPDATE=true
- WATCHTOWER_HTTP_API_METRICS=true
- WATCHTOWER_HTTP_API_TOKEN=mytoken
- WATCHTOWER_HTTP_API_PERIODIC_POLLS=true
- DOCKER_TLS_VERIFY=true
- WATCHTOWER_NOTIFICATIONS=slack
- WATCHTOWER_NOTIFICATION_SLACK_HOOK_URL=https://hooks.slack.com/services/XXXXX
- WATCHTOWER_NOTIFICATION_SLACK_IDENTIFIER=watchtower-2
- WATCHTOWER_NOTIFICATION_SLACK_CHANNEL=#Crispymy homepage services.yaml entry reads thus: - Watchtower:
icon: https://github.com/walkxcode/dashboard-icons/raw/main/png/watchtower.png
href: http://192.168.1.64:8080
widget:
type: watchtower
fields: ["containers_scanned", "containers_updated", "containers_failed"]
url: http://192.168.1.64:8080
key: mytokenlike you, i was totally stuck on how to create or find a watchtower api key of some kind, until someone explained to me it's just generated in the compose file itself. So in the example above, it's literally "mytoken", in both the compose and the homepages yamls hope this helps |
Beta Was this translation helpful? Give feedback.
-
|
oh also i must give all credit to @henkiewie who patiently walked me through this and therefore, by proxy, you also. |
Beta Was this translation helpful? Give feedback.
-
|
Good job figuring this out together! I'm mainly excited by homepage, which I've never heard about or seen before. 😅 |
Beta Was this translation helpful? Give feedback.
-
it's the best of the dashboards i've tried by quite some way
|
Beta Was this translation helpful? Give feedback.
-
|
The authentication by a key supplied by the user is a bit uncommon, yeah. It's in a way the same as specifying |
Beta Was this translation helpful? Give feedback.
-
i think a simple "You choose the API key yourself, the same way you'd choose a password. We don't create one for you so use something secure and memorable" would be fine. Like the OP here I spent ages hunting around the documentation completely baffled that there didn't seem to be a way of creating or finding an API key like, literally, every other service I self host. If i hadn't searched the archive of issues on github, found the one guy who was having the same problem months ago, asked him if he fixed it and him walking me through it I would have easily just given up.. which seems... suboptimal? |
Beta Was this translation helpful? Give feedback.
-
|
can confirm this all worked fine in homepage once the schedule ran in watchtower.
|
Beta Was this translation helpful? Give feedback.
-
|
I keep forgetting to reply to this but yes! it all works perfectly for me. Thank you so much for coming to my rescue on this. I was going maaaaaad ahahaha. |
Beta Was this translation helpful? Give feedback.
-
|
Hi everyone, I recently installed Watchtower through Portainer on Docker, installed on a Debian based LXC container. and that give me back the following result but nothing else. I cannot even ping the local address 192.168.1.126:8080. something happens because I receive an API Error as shown below |
Beta Was this translation helpful? Give feedback.
-
|
There is no href for wartchtower (no webpage) or ping. |
Beta Was this translation helpful? Give feedback.
-
|
Ok for href, ping and Gmail port. The value "key" in my compose is without quotes; it was an example, I probably used the wrong character. |
Beta Was this translation helpful? Give feedback.
-
|
Look at documentation here; https://containrrr.dev/watchtower/http-api-mode/ |
Beta Was this translation helpful? Give feedback.
-
|
Ciao. Ok I made some changes you suggested. Added LOG_LEVEL and TRACE set as true. In the log,I'm able to see If I run Now, it seems I have an additional problem. After having set showStatus= false in the settings.yaml (leaving true only for some elements in services.yaml). I cannot see even the part that shouldbe dedicated to the widget |
Beta Was this translation helpful? Give feedback.
-
|
Out of ideas. If there is no answer from the curl -H command your watchtower container is still missing something. |
Beta Was this translation helpful? Give feedback.
-
|
Ciao henkiewie. An update....a part that I'm a total stupid. After having substituted the "mytoken" with the real token of mine, the curl command gave me this: I made another try on another machine and the results of curl is the same. To be highlighted that in this second machine I was receiving a 401 error but, after having put another token with only letters and numbers, I don't receive any more errors but the fact that nothing appears: |
Beta Was this translation helpful? Give feedback.
-
|
It must be. Mine looks like this; |
Beta Was this translation helpful? Give feedback.
-
|
Finally, I got it. By chanche (and don't know why I tried it) I commented the line |
Beta Was this translation helpful? Give feedback.
-
|
I am already using Port 8080 for pihole. What now? How to change the port for the http API for watchtower? |
Beta Was this translation helpful? Give feedback.
-
|
Look at the docker-compose.yml in the thread above. Change the first number to a free tcp port. like 8081:8080 |
Beta Was this translation helpful? Give feedback.
i went through literally this exact situation earlier this morning. In fact I did a double take thinking i'd posted your comment under a different name somehow, it was that similar.
Anyway, after a lot of digging around and fiddling, I got it working. This is my working compose yaml which just notifies of updates instead of automatically updating them (
WATCHTOWER_MONITOR_ONLY=true), sends updates to my slack channel (you don't have to use this) and is working with homepage: