Another orphaned container issue

[bobbintb]

Every once in a while, I will go to the docker tab and there will be an orphaned image or two. I remove them and reinstall with the previous template but it keeps happening. I've looked at threads with similar issues. I don't have the Advanced Buttons plugin installed. I've deleted the img before. I have CA set to update my dockers automatically at around 3am or so. I'm not sure why they get orphaned. It's not frequent, but it happens occasionally. I don't see anything in the logs that's blatantly obvious to someone that doesn't know what to look for. Any ideas?

[trurl]

4 hours ago, bobbintb said:

Any ideas?

Not without diagnostics when the problem occurs

[bobbintb]

On 8/23/2021 at 4:33 PM, trurl said:

Not without diagnostics when the problem occurs

tower-diagnostics-20210830-2124.zip

I wasn't sure when it was occurring so it took a while to figure it out. Nagios noticed a change on 08-30-2021 05:58:51 to the qbittorrent docker.

[trurl]

 Not obviously the cause of your problem, but it does make me wonder about how you have things configured

Aug 29 04:30:02 Tower root: Fix Common Problems: Warning: Share isos set to not use the cache, but files / folders exist on the cache drive ** Ignored
Aug 29 04:30:02 Tower root: Fix Common Problems: Warning: Share server set to not use the cache, but files / folders exist on the cache drive ** Ignored
Aug 29 04:30:02 Tower root: Fix Common Problems: Warning: Share VMs set to not use the cache, but files / folders exist on the cache drive ** Ignored

For some reason though, FCP doesn't say anything about your Docker share, which you are using the way most use the appdata share. Your Docker share is set to use cache only, but it has files on the array.

 

And you apparently have CA Backup configured to only backup the part of that Docker share which is on cache

Aug 29 03:01:58 Tower CA Backup/Restore: Backing Up appData from /mnt/cache/Docker/

so the backup is missing the parts that are on the array.

Is all that really the way you intend for things to be?

 

[bobbintb]

16 hours ago, trurl said:

Is all that really the way you intend for things to be?

I don't even know anymore. I know I need to go through and take another look at how I have things configured. I didn't think I had anything related to the dockers on the array. I mean, many of them save files to the array, but there shouldn't be any sort of config files or anything anywhere other than the docker share on the cache drive.

Edited August 31, 2021 by bobbintb

[trurl]

What do you get from the command line with these?

ls -lah /mnt/disk9/Docker

and

ls -lah /mnt/disk8/VMs

 

[bobbintb]

root@Tower:~# ls -lah /mnt/disk9/Docker
total 0
drwxrwxrwx 2 nobody users  6 Mar 26  2017 ./
drwxrwxrwx 5 nobody users 71 Aug 29 04:30 ../
root@Tower:~# ls -lah /mnt/disk8/VMs
total 0
drwxrwxrwx 2 nobody users  6 Nov 28  2018 ./
drwxrwxrwx 5 nobody users 84 Aug 29 04:30 ../
root@Tower:~# 

 

[trurl]

OK looks like those are empty.

 

 

You can fix those FCP warnings by cleaning those things up, but it won't really help with your problem.