After taking the array offline and adding my first parity disk, all my dockers have disappeared from the docker tab

[whiterook6]

Up until yesterday I was running unraid with two large hard drives, no cache and no parity. I just added another HDD and NVMe and decided to enable parity and cache. Now all of my docker containers have disappeared from the docker tab. Will they come back when the parity check is complete? Is this similar to how turning off the array also stops the docker containers? To be clear, my docker containers haven't turned off, they've completely vanished from the tab.

 

If they have gone missing or been removed for some reason (I swear I didn't do it on purpose) what are the odds that I can restore them with the same configuration as before? Or will I have to rebuild everything from scratch? I had the official plex docker as well as linuxserver's nzbget, sonarr, and radarr installed.

 

Thanks.

 

Screenshots:

 

[JorgeB]

As long as you have the appdata you can easily recreate the image:

 

https://docs.unraid.net/unraid-os/manual/docker-management/#re-create-the-docker-image-file
Then:
https://docs.unraid.net/unraid-os/manual/docker-management/#re-installing-docker-applications
Also see below if you have any custom docker networks:
https://docs.unraid.net/unraid-os/manual/docker-management/#docker-custom-networks

[whiterook6]

Thanks for the links. Most of the dockers could be recreated fine, but I had to rebuild plex's libraries _again_.

 

Any idea what could've caused it? Or how to prevent this in the future? I don't know where these dockers are stored or what can delete them.

[JorgeB]

Make sure of you have an appdata backup.

[Bastian]

On 8/15/2024 at 10:41 PM, whiterook6 said:

Thanks for the links. Most of the dockers could be recreated fine, but I had to rebuild plex's libraries _again_.

 

Any idea what could've caused it? Or how to prevent this in the future? I don't know where these dockers are stored or what can delete them.

The Docker Tab only shows Docker Containers. They are runtimes created from Docker Images. I don't want to exclude any fault on unraids part, but it can happen from time to time, that the Docker Daemon just can't start them. Nowadays less often, but you can still find bug reports about it. Happened with my Containers once or twice, with Docker Networks from time to time.

 

Docker Containers aren't meant to be long-living or have sensitive data within their filesystem. They are meant to be able to be destroyed and re-created any time. That's why all the important stuff has to be mounted to the host filesystem. That's also why we have the templates. They store all the information on how the Container gets created. Keep your templates clean and tidy and you can recover such a case by just spinning all Containers back up again. A template is comparable to a runtime of an image (that's why you ca have multiple template for the same image, they just have to be named differently).

[whiterook6]

On 8/21/2024 at 10:44 AM, Bastian said:

The Docker Tab only shows Docker Containers. They are runtimes created from Docker Images. I don't want to exclude any fault on unraids part, but it can happen from time to time, that the Docker Daemon just can't start them. Nowadays less often, but you can still find bug reports about it. Happened with my Containers once or twice, with Docker Networks from time to time.

 

Docker Containers aren't meant to be long-living or have sensitive data within their filesystem. They are meant to be able to be destroyed and re-created any time. That's why all the important stuff has to be mounted to the host filesystem. That's also why we have the templates. They store all the information on how the Container gets created. Keep your templates clean and tidy and you can recover such a case by just spinning all Containers back up again. A template is comparable to a runtime of an image (that's why you ca have multiple template for the same image, they just have to be named differently).

Makes sense. But when I recreate the docker containers from the same images, I still have to go through and set up the settings and libraries and downloaders and so on. I suppose that's the fault of the app itself, right?

[JorgeB]

That suggests you are not using the original appdata folder.

[Bastian]

On 8/22/2024 at 10:18 PM, whiterook6 said:

Makes sense. But when I recreate the docker containers from the same images, I still have to go through and set up the settings and libraries and downloaders and so on. I suppose that's the fault of the app itself, right?

Sounds more like a configuration issue on your part. From that list I only know Plex and that should be able to survive a re-creation. Sometime the online service gets confused and you have to pin the libraries anew, but not the entire setup. Best to check your mount-bind against the official documentation. You can easily test it by just deleting the service. After creation from the template it should be like before.