updating containers to latest version if not automatically done

Posted by currentlylive

So I noticed sabnzbd is on 5.0.3 but my image of it is on 4.4.1, I just did a update pull through sparkbox but sabnzbd is still in 4.4.1. Just wondering how to go about update this image version or any container image version if it is not doing it automatically?

1 replies

tomspark wrote:

The issue is that sparkbox update pulls the latest image but doesn't recreate the container if it's already running — Docker keeps the old one alive. You need to force a rebuild: sparkbox restart sabnzbd. That will stop the container, pull the new image, and spin up 5.0.3. If you want to update everything at once and be sure all containers get the latest images, run sparkbox down && sparkbox up — that tears down all services and rebuilds them fresh from whatever images are now on disk. What version of SparkBox are you running? (cat /opt/sparkbox/VERSION) — if you're on 1.6.145 or later, sparkbox update is supposed to auto-restart containers, so there might be a bug if that's not happening.