Docker Watchtower container restarting and mm container errors after upgrade

sdetweil

@scottwalsh @karsten13 will have to help

MMOs is on pi os I think

karsten13

there is a line

WATCHTOWER_IMAGE="containrrr/watchtower:latest"

in the file /opt/mm/run/.env.

Can you change this to

WATCHTOWER_IMAGE="ghcr.io/nicholas-fedor/watchtower:latest"

and restart with

cd /opt/mm/run
docker compose up -d

Background is that the original watchtower is unmaintained and I suspect the original image is to old now. The new image is from a maintained fork, I use this already in other setups.

scottwalsh

@karsten13

Thank you for that. The Watchtower seems to be running fine now.

Did you have any thoughts on these errors that appear in the mm container? Seems to be running fine.

[Extract]

scottwalsh@calendar:/opt/mm/run $ docker logs mm
[2026-01-02 14:09:18.082] [LOG]   [app] All module helpers loaded. 
[2026-01-02 14:09:18.105] [LOG]   [server] Starting server on port 8080 ...  
[2026-01-02 14:09:18.113] [WARN]  [server] You're using a full whitelist configuration to allow for all IPs 
[2026-01-02 14:09:18.226] [LOG]   [app] Server started ... 
[2026-01-02 14:09:18.229] [LOG]   [node_helper] Connecting socket for: MMM-mmpm 
[2026-01-02 14:09:18.231] [LOG]   [node_helper] Starting module helper: MMM-mmpm 
[2026-01-02 14:09:18.233] [LOG]   [node_helper] Connecting socket for: calendar 
[2026-01-02 14:09:18.235] [LOG]   [calendar] Starting node helper for: calendar 
[2026-01-02 14:09:18.236] [LOG]   [node_helper] Connecting socket for: MMM-AVStock 
[2026-01-02 14:09:18.239] [LOG]   [node_helper] Connecting socket for: MMM-anotherNewsFeed 
[2026-01-02 14:09:18.240] [LOG]   [MMM-anotherNewsFeed] Starting node helper for: MMM-anotherNewsFeed 
[2026-01-02 14:09:18.242] [LOG]   [node_helper] Connecting socket for: updatenotification 
[2026-01-02 14:09:18.243] [LOG]   [node_helper] Starting module helper: updatenotification 
[2026-01-02 14:09:18.245] [LOG]   [app] Sockets connected & modules started ... 
[21:0102/010919.030995:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[2026-01-02 14:09:19.430] [LOG]   [electron] Launching application. 
[21:0102/010919.848714:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: 
[21:0102/010919.850527:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[21:0102/010919.852228:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[21:0102/010919.852910:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[21:0102/010919.860171:ERROR:dbus/bus.cc:408] Failed to connect to the bus: Failed to connect to socket /var/run/dbus/system_bus_socket: No such file or directory
[21:0102/010919.860444:ERROR:dbus/object_proxy.cc:573] Failed to call method: org.freedesktop.DBus.NameHasOwner: object_path= /org/freedesktop/DBus: unknown error type: 
[2026-01-02 14:09:23.059] [INFO]  [utils]

karsten13

@scottwalsh said in Docker Watchtower container restarting and mm container errors after upgrade:

Did you have any thoughts on these errors that appear in the mm container? Seems to be running fine.

they are only noise, you can ignore them.

I thought I sorted out the dbus errors but they are back again, will update my setup so they disappear in the future.

karsten13

I found a good documented PR in another project which explains the dbus errors in detail.

scottwalsh

@karsten13 said in Docker Watchtower container restarting and mm container errors after upgrade:

I found a good documented PR in another project which explains the dbus errors in detail.

Thanks for providing the link, interesting background.