Docker Containers show version 'not available'


Recommended Posts

My Unraid server has been working fine for a while, but recently it seems to be having problems with the Docker Containers.  All of them show up with version 'not available' and as a result i can't update them.

 

I've attached the diagnostics simply because I have to assume it is networking in some way.  

 

Before today it was set up with Eth0 bonded to eth0/1/2/3.  I changed that to only bonding with eth0/1 and plugged in eth1.  I did that hoping it would resolve the issue.  previously none of 1/2/3 were plugged in.

 

Hopefully someone has some insights

tower-diagnostics-20200802-1129.zip

Link to comment
12 minutes ago, johnnie.black said:

You can first try using the command line, or your favorite copy tool like midnight commander or krusader, note that it's good practice making regular backups of those files, both the appdata folder and libvirt.img (if you have VMs).

I have Krusader on there, but it is a docker and no longer working due to this corruption issue.  :(  I will have to figure out command line I guess.

Link to comment
1 minute ago, johnnie.black said:

Those errors are likely the result of data corruption, btrfs will give an i/o error if corruption is detected so that you're not fed bad data without knowing, would need diags to confirm, if it's that you can use btrfs restore to bypass it, but data will still be corrupt.

 

I really don't think I need to worry about that data right?  I believe all that data is located at /mnt/user/appdata anyway.  I have no VMs, just Docker containers.

Link to comment
1 minute ago, johnnie.black said:

/mnt/cache/appdata is in /mnt/user/appdata

So you are saying if I want my dockers to retain their settings - I need to recover that.  Sound about right?

 

Sorry for all the questions - I'm not all that familiar with Unraid yet.  I've only had it running for 6 months and mostly left it alone after setup.

Link to comment
15 minutes ago, johnnie.black said:

Nothing as long as the data fits on disk1, if it doesn't you'll need to use another disk with more space.

 

Also good idea to cancel/pause the parity check for nw.

 

Don't I have to do something with the cache drive?  Like, format, replace, something?  I'm not real sure where to do that since the cache drive is live.  

Link to comment
1 hour ago, Convington said:

Man does Plex have a lot of files in there :(  I would have thought most would be in the array, something I will have to look at after I finally get this back up and running

Keeping appdata (and system) on cache is the usual way. If you have those on the array dockers will have performance impacted by the slower parity writes, and will also keep array disks spinning since those files will be open.

Link to comment

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.