Bug: Containers with network dependencies fail to start from time to time

[AN1MATEK]

Hello there,

This issue happens only sometimes, like once every 10/15 backups.

I have a container that is a VPN tunnel, PIA. There are 3 other containers that have Network Type: Custom container:pia

The VPN container starts always first. When the other 3 start after the backup, they fail, as they are looking for a container id for their network and this has changed. I have a stupid fix in place in the post-run script that checks if the containers are running or not, and then executes the whole docker run, as it is displayed when starting from the UI. They come up without an issue.

if docker ps --filter "name=thelounge" --filter "status=running" | grep -q "thelounge"; then
    echo -e "Container thelounge is running\n"
else
    echo -e "Container thelounge is not running.\n"
    /usr/bin/docker remove thelounge
    /usr/bin/docker run -d --name='thelounge' --net='container:pia' [...]'

Since I have this fix in my script I don't have issues anymore, other than the red notifications when it happens. I wanted to bring attention to it.

Thank you for the development efforts. The plugin is staple for me.

Issue in unRAID forums: https://forums.unraid.net/topic/137710-plugin-appdatabackup/?do=findComment&comment=1470903

Debug log ID: 4b60e7f5-421c-45b4-abcf-74730e670f60

[berubejp]

I have the same issue. I've got containers behind a vpn (with --net='container:myvpncontainer') and they all fail to restart after backup most of the time (maybe 75%).
I also created a dumb script that would docker start xx them after the backup but I get a No such container error. Strangely, if I browse to the Unraid docker page then start the script, it works...

[AN1MATEK]

As you see in my script, you have to remove the old container and do docker run .... Just copy what I did and it will work.

[berubejp]

Yeah that's what I did and it worked, thanks. But having to keep configurations updated in 2 places is not perfect.

[PilaScat]

same issue
debug id 868ba415-051b-42e2-b406-3f626a882054