Has anyone ever had dockers disappear? My sonarr docker was "unresponsive" so I rebooted my server. When it was back online, sonarr, CP, krusader, dropbox and plex were no longer installed. Very strange!

 

I guess nothing to be done and I will set them up again? All the data is there...kind of a pain though...

Post a screenshot of your Settings - Docker page.

 

Has anyone ever had dockers disappear? My sonarr docker was "unresponsive" so I rebooted my server. When it was back online, sonarr, CP, krusader, dropbox and plex were no longer installed. Very strange!

 

I guess nothing to be done and I will set them up again? All the data is there...kind of a pain though...

Have you checked that the share holding docker is set to be cache only?

@trurl - image attached.

 

@itimpi - is this where the docker image is kept? Mine is at /mnt/cache/docker.img

 

 

I started to add my missing dockers back and now get errors when adding plex. See attached.

 

My big concern is that my Crashplan (which was all done) may now also be corrupt?

 

Really no idea what could have happened - all has been working like a champ.

@trurl - image attached.

 

@itimpi - is this where the docker image is kept? Mine is at /mnt/cache/docker.img

In that case the docker.ing file is not inside a folder so it will not show up a share.

 

However, do you have an appdata folder on the cache drive where the configuration files for docker (and normally any temporary work files) are stored.  If so then you will have an appdata share, and the appdata share must be set as cache only.  The same would apply to any other top level folders on the cache drive that are meant to stay there and not be moved to the array data drives.

 

Note that if there is a problem with your docker.img file then the easiest thing to do is to stop docker, delete it and then start docker again to get the images downloaded again.  You  might want to also consider increasing the size of the docker.img file if it is running out of space (although that is often due to a misconfigured docker storing files inside a container that should really be stored outside it).

 

My appdata folder is at /mnt/cache/appdata. And this is cache only.

 

Yesterday I did try to install Mylar. It failed and I was busy so just left it....did not dig deep into it.

 

OK. I deleted my image docker.img and bumped the size from 10GB to 20GB.

 

All is working fine now (Crashplan has been "still around" but acting flaky). Crashplan is fine and it is pretty easy to add my dockers back.

 

But I have to admit, this scares me a bit?

 

OK. I deleted my image docker.img and bumped the size from 10GB to 20GB.

 

All is working fine now (Crashplan has been "still around" but acting flaky). Crashplan is fine and it is pretty easy to add my dockers back.

 

But I have to admit, this scares me a bit?

One of the points of dockers is that if properly set up all transient data is stored externally to the docker containers so that it is easy to delete the containers and redownload them if any problems occur. Ideally this should not happen and it does mean that you have to take the download cost of getting the images again. unRAID set up the my_templates templates set which contains all the configuration information you have set up so that re-instating a docker does not mean it needs to be configured again.

 

Docker does not seem to handle very well the case of the docker.img file getting full so you might want to periodically look at the space being sued.

 

It is cool that it seems easy enough to add these back.

 

Still having some weirdness. Anyone ever see anything like the attached?

 

Note the names :-)

Those are failed installs from when docker.img was full.  Its safe to delete them.