Closed SivertGullbergHansen closed 2 months ago
Just pushed a fix - please let me know if it still occurs (latest-image, v1.4.0)
Thanks for the very quick response! That was extremely quick to what I'm used to 😄
I am using the docker and with the "latest" tag it doesn't seem to update, but switching to "v1.40.0" seems to work, and it seems its fixed :) Thanks again!
Glad it works now.
I saw that you also created a fork originally from matt dlg‘s script. Let me know it you have any ideas how to develop this one further (has its roots also on matts script)
Re „latest“: to get it to work with the latest tag again, you may need to delete the container&image from your system (can be done via cmd line or portainer)
you may be interested in a watchtower, which does automated upgrades to your containers.
here's my config, just for your reference in case interested.
# WatchTower - Automatic Docker Container Updates
watchtower:
<<: *common-keys-core
image: containrrr/watchtower:latest
container_name: watchtower
volumes:
- /var/run/docker.sock:/var/run/docker.sock
environment:
WATCHTOWER_CLEANUP: "true"
WATCHTOWER_REMOVE_VOLUMES: "true"
WATCHTOWER_INCLUDE_STOPPED: "true"
WATCHTOWER_NO_STARTUP_MESSAGE: "false"
WATCHTOWER_SCHEDULE: "0 26 12 * * *" # Everyday at 12:30
DOCKER_API_VERSION: "1.40"
<<: *default-tz-puid-pgid
What I've done so far:
The container logs are constantly logging this:
Any ideas? The debug log doesn't show any errors or warnings. Checks all instances, they are ok 200, afterwards:
And contains all of my active torrents it seems