March 9Mar 9 HiI have been trying to get my server setup for 5-6 days and I've been running into issues.Hardware:Gigabyte Z790 Aorus Elite AXIntel i5 12600kCorsair Vengeance DDR5 2x8GB 5200mhz2 20TB Barracuda drives (shucked from expansion drives)I ran a memtest for 15ish hours and it passed with no errors. My drives show no errors. I check the logs before the crash and there are no errors. Attached is the most recent log file before the crash. You can see that I log in, enable docker, and stop the one container I have installed. I let the server run with just docker enabled and it crashes. When I have docker disabled it runs with no issue. syslog-previous.txt
March 9Mar 9 Community Expert Does it stil crash with the Docker service enabled and the container stopped?
March 9Mar 9 Author 3 minutes ago, JorgeB said:Does it stil crash with the Docker service enabled and the container stopped?Yes, the diagnostics I provided are when it crashed with just the docker enabled and no containers started.
March 9Mar 9 Author Small update, the one thing I hadn't tried was switching from macvlan to ipvlan in docker settings. I did that and enabled docker with containers stopped. So far it has been running smoothly, uptime almost 2 hours.
March 9Mar 9 Community Expert Your diagnostics were actually without docker service started.Setup syslog server
March 9Mar 9 Author 6 minutes ago, trurl said:Your diagnostics were actually without docker service started.Setup syslog serverSorry, just want to make sure I'm understanding. I currently have the mirror to flash option as "yes". Do I also have to set local syslog server to "enabled"?
March 9Mar 9 Community Expert I think you have it right. Both syslog and syslog-previous showed docker service starting, then syslog showed it being stopped, so docker.img was not actually mounted when the diagnostics were taken.Neither syslog showed anything about crash.
March 9Mar 9 Author Right, so that's the issue. I've checked the logs every time it crashes and there's nothing indicating a crash or errors. I found an older post on here referencing crashes when docker uses macvlan.Since restarting the server and switching docker to ipvlan it has not crashed yet, when normally it would have. I wonder if that has something to do with it? @JorgeB stated in a comment on that thread that having macvlan with bridging enabled could cause issues. I didn't change any network default settings until now, so it defaults to macvlan in docker with network settings having bridging and bonding enabled.This is the post for reference:https://forums.unraid.net/topic/151441-macvlan-crashes-6126/page/2/ Edited March 9Mar 9 by Wieldy
March 9Mar 9 Community Expert 25 minutes ago, Wieldy said:I found an older post on here referencing crashes when docker uses macvlan.This is no longer an issue since Unraid 6.12.11
March 9Mar 9 Author 1 minute ago, JorgeB said:This is no longer an issue since Unraid 6.12.11Ok, but I will say, that since switching to ipvlan there are no crashes yet. Coming up on 3 hours running ipvlan with one docker enabled using a custom network. Bonding and bridging are still enabled.Does anyone have theories as to why having docker use macvlan would cause a crash?
March 9Mar 9 Author Well, it crashed again with docker setting to ipvlan. I restarted the server disabled bonding and bridging and turned on docker with no containers. Docker is using macvlan since bonding and bridging are turned off.I'm really starting to give up here. I ran memtest and it passed I've run docker in default settings with no containers enabled and it crashedI ran docker in ipvlan with no containers enabled and it crashed.I don't enable docker and the server runs fine.No errors on disksNo errors in log files.Attached are the most recent log files. apollo-diagnostics-20260309-1212.zip
March 9Mar 9 Community Expert Recommend setting it to save to a share, not the flash drive, as that can miss something if the flash drive is the problem, then add it separately since it doesn't'come with the diags.
March 9Mar 9 Author Ok, I fixed that. I guess I'll enable a container and get it to crash again to see if the logs changes.
March 14Mar 14 Community Expert Docker also logs to /var/log/docker.log, and that might contain the issue you're having. Somehow it doesn't end up in syslog.Next time be sure to grab that file before rebooting / restarting the service.
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.