So, right out the gate, I realize Watchtower has been abandoned. I get that. Still, it’s a great app. 95% of the time, it works every time.
The issue I have is as follows:
INFO[93549] Found new searxng/searxng:latest image (5613a99caf5d)
INFO[93565] Found new prom/prometheus:latest image (b5239da13ab0)
INFO[93584] Found new ghcr.io/karakeep-app/karakeep:latest image (c5fcb1a653c6)
INFO[93592] Stopping /CADVISOR-PROMETHEUS (342680d2a684) with SIGTERM
INFO[93593] Creating /CADVISOR-PROMETHEUS
INFO[93594] Stopping /SEARXNG (0842827f17a9) with SIGTERM
INFO[93597] Creating /SEARXNG
ERRO[93597] Error response from daemon: the container-wide MAC address must match the endpoint-specific MAC address for the main network, or be left empty
INFO[93597] Removing image 9e24e9a9806c
INFO[93597] Session done Failed=1 Scanned=38 Updated=2 notify=no
It doesn’t do this everytime, and it’s not one particular container. It seems random. For the example of SearxNG, I have not specified a MAC address.
spoiler
docker run -d \
--name searxng \
-p 8989:8080 \
-v /srv/docker/searxng/data:/etc/searxng \
-e SEARXNG_BASE_URL="https://" \
-e SEARXNG_INSTANCE_NAME="SearxNG" \
-e SEARXNG_CONTACT_INFO="mail.com" \
-e SEARXNG_LANGUAGE="en-US" \
-e SEARXNG_AUTOCOMPLETE="duckduckgo" \
-e SEARXNG_THEME="simple" \
-e SEARXNG_OUTGOING_METHOD="default" \
-e SEARXNG_ENABLE_METRICS="true" \
-e SEARXNG_ENABLE_CAPTCHA="false" \
-e SEARXNG_ENABLE_INFINITE_SCROLL="true" \
-e SEARXNG_ENABLE_PIWIK_ANALYTICS="false" \
-e SEARXNG_ENABLE_ADVANCED_SEARCH="true" \
-e SEARXNG_ENABLE_PRIVATE_RESULTS="true" \
-e SEARXNG_ENABLE_TORIFICATION="false" \
-e SEARXNG_ENABLE_HTTPS_EVERYWHERE="true" \
-e SEARXNG_ENABLE_PROXY="false" \
-e SEARXNG_ENABLE_PLUGINS="true" \
searxng/searxng
In fact, I’ve never specified a specific MAC for any of my containers, and just let Docker do what it do. I’m just wondering if anyone has run up on this issue, and what did you do to remediate it, besides use another updater app? I like Watchtower, but only 95% of the time. LOL
It’s not a huge issue spinning the container back up. Takes less than 30 sec. However, that’s not how it’s supposed to work, so I seek input.
Did not know it was abandoned, will look thru all this tonight.
Personally having great results with Diun. Same idea (check for newer container image) and works 100% for me.
Don’t know if it can automatically load and restart containers, rather do that personally.
It’s on the list.
Here is a fork of watchtower that is meant to keep things up to date that might work for you. I haven’t tried it yet but am setting it up now.
Thanks, I’ll give it a go
time="2025-06-30T17:27:53Z" level=info msg="Watchtower 2.3.2" time="2025-06-30T17:27:53Z" level=info msg="Using no notifications" time="2025-06-30T17:27:53Z" level=info msg="Checking all containers (except explicitly disabled with label)" time="2025-06-30T17:27:53Z" level=info msg="Scheduling first run: 2025-07-01 17:27:53 +0000 UTC" time="2025-06-30T17:27:53Z" level=info msg="Note that the first check will be performed in 23 hours, 59 minutes, 59 seconds"We’ll see.
If anyone is interested in just a simple image updates monitoring, check out cup.I know its not exactly what you want (it doesn’t do the update), but I stumbled on it quite by accident and I like the simplicity.
