Skip to content
View in the app

A better way to browse. Learn more.

Unraid

A full-screen app on your home screen with push notifications, badges and more.

To install this app on iOS and iPadOS
  1. Tap the Share icon in Safari
  2. Scroll the menu and tap Add to Home Screen.
  3. Tap Add in the top-right corner.
To install this app on Android
  1. Tap the 3-dot menu (⋮) in the top-right corner of the browser.
  2. Tap Add to Home screen or Install app.
  3. Confirm by tapping Install.

What is going on with my Docker?

Featured Replies

I moved my server to a new location, and everything seemed fine until I noticed an issue with 1 container corrupted after the move (plex).

 

I reinstalled it, and it worked at first, but then my server locked up and restarted, and it was corrupted again.

 

I thought it was just that container, but then it started happening to other ones (bazzar, delugevpn, pihole, gauacamole, etc.).

 

I searched online for solutions, and found some people suggesting switching my cache pool from btrfs to zfs, so I did that, but the issue still happens.

I also found suggestions for switching to ipvlan, which won't work for me, so I followed the steps here to keep macvlan enabled: https://docs.unraid.net/unraid-os/release-notes/6.12.4/#fix-for-macvlan-call-traces

 

I had a couple more crashes after that while trying to reconfigure the dockers, but nothing major.
I was even able to reinstall plex, and get hardware transcoding using my nvidia gpu working.

 

I then started reenabling dockers one by one, which seemed fine.

 

I then tried to update some CPU pin settings for the dockers under settings, and it locked up and crashed again.

 

Now its booting up like this. and I don't know what to do to fix it except keep reinstalling containers, just for it to crash again...

 

Diagnostics attached.

 

EDIT:

Unraid version 6.12.6

Docker is disabled after every crash/restart and i have to enable it again.

The "edit" option is now gone from any of the remaining containers that were left running, so I can't do anything with them.

Fix Common Problems is reporting a bunch of corrupt XML files now.

My Docker CPU pinning is now completely blank.

 

dockers.thumb.png.f3a32d448b7cf075496938554f8db69d.png

 

image.png.7d3f111e6c4c426c23a84706ef4152f2.png

 

image.thumb.png.ab4f2c62a2b6eaea495560cf3ebe5b6e.png

 

image.thumb.png.1b6f6eb83333c27938a4685bcfae930a.png

 

 

 

diagnostics-20250418-1552.zip

Edited by carnivorebrah
additional info, grammar/spelling

  • Community Expert
3 hours ago, carnivorebrah said:

Fix Common Problems is reporting a bunch of corrupt XML files now.

Those are your docker templates on the flash drive.

 

Do you have a recent backup of flash?

  • Author
1 hour ago, trurl said:

Those are your docker templates on the flash drive.

 

Do you have a recent backup of flash?

 

Yes, I backed up everything prior to doing the ZFS reformat and disabling bridging for macvlan.

 

I see them in the backup.

 

Should I just restore the XML files from the flash backup?

 

EDIT: Okay, restoring each XML is allowing me to reinstall each docker with the settings remembered, which is good. Only thing I'm worried about now is the next crash. I tried running a Memtest from the Unraid boot menu, but it just automatically closes after running for awhile and reboots. I can't seem to catch it to see if it's completing. I'm not seeing any errors after about 20+ minutes of it running. I ordered more memory to swap out in case that is the issue. I really don't know what else to do.

 

EDIT 2: And the whole server crashed again after I went through and reinstalled every container except Plex. I don't get it....

Edited by carnivorebrah

  • Community Expert
14 hours ago, carnivorebrah said:

tried running a Memtest from the Unraid boot menu

Not sure that old version of Unraid has the latest memtest.

 

Try booting memtest86 from another flash drive.

  • Author

Ran the memtest, and after 16 hours, it found 0 errors during 1 of 4 passes.

I don't have time to wait 96 hours for it to complete, and I don't think this is a memory issue.

 

I rebooted it and started plex, and it crashed soon after while simply scanning the library files.

It doesn't just crash with plex either. It happens with pretty much any container. Plex is just easiest to reproduce it on, and the one this all started with.

 

Tried switching to docker directory instead of vdisk image, and it crashed while i was simply stopping the containers that I had installed because I was about to try to install Plex.

 

I give up and will be throwing this thing away. Its a complete waste of time, if something as simple as stopping, starting or updating a container is going to cause the entire thing to crash, and there not be any way to fix it.

 

Absolute nightmare.

Edited by carnivorebrah

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...

Account

Navigation

Search

Search

Configure browser push notifications

Chrome (Android)
  1. Tap the lock icon next to the address bar.
  2. Tap Permissions → Notifications.
  3. Adjust your preference.
Chrome (Desktop)
  1. Click the padlock icon in the address bar.
  2. Select Site settings.
  3. Find Notifications and adjust your preference.