Stopped updating Qbittorrent correctly

[bluskye]

This started recently, but worked perfectly until recently, see log file, qbittorrent isn't updating correctly, been a few weeks now, not sure how to debug this log file. I have to manually pull the image from portainer to get qbitorrent back up. It only happens with qbitorrent, which is very odd.

I have a Portainer stack launching gluetun (VPN) + qbitorrent

time="2026-02-07T21:27:14Z" level=info msg="Found new image" container=gluetun image="qmcgaw/gluetun:latest" new_id=802593c3788d
time="2026-02-07T21:27:16Z" level=info msg="Stopping container" container=gluetun id=0e2e02205b30 signal=SIGTERM timeout=30s
time="2026-02-07T21:27:19Z" level=info msg="Started new container" container=gluetun id=0e2e02205b30 new_id=304c8cdc4e64
time="2026-02-07T21:27:19Z" level=info msg="Removing image" image_id=0f03e6ef61fb image_name="qmcgaw/gluetun:latest" notify=yes
time="2026-02-07T21:27:19Z" level=info msg="Update session completed" failed=0 notify=no scanned=8 updated=1
time="2026-02-08T09:27:12Z" level=warning msg="Unable to resolve network container" container=qbittorrent container_id=f326624c7546c922ab4f16cd7700a63a38bc65642008c4edf083e85b346df4bf error="Error response from daemon: No such container: 164e0720338653e50daf94b8b181751490ff26dacbc7955f5b44979fe2319731" network_container=164e0720338653e50daf94b8b181751490ff26dacbc7955f5b44979fe2319731
time="2026-02-08T09:27:27Z" level=info msg="Found new image" container=qbittorrent image="lscr.io/linuxserver/qbittorrent:libtorrentv1" new_id=9a6dfefdc326
time="2026-02-08T09:27:28Z" level=info msg="Stopping container" container=qbittorrent id=f326624c7546 signal=SIGTERM timeout=30s
time="2026-02-08T09:27:34Z" level=info msg="Update session completed" failed=1 notify=no scanned=8 updated=0

[nicholas-fedor]

The problem that you're seeing is related to dependent containers not being started in the correct order.

This is related to Issues #1299 and #1306

I'm expecting PR #1307 will help with addressing the underlying issue.

[bluskye]

Thanks, didn't realize this was a thing, ill hang tight

[nicholas-fedor]

Version 1.14.2 has been released, which is expected to resolve the problem that you were seeing.

[bluskye]

TY you so much! Will give it a shot