lmag

Can you describe the general steps I should follow to do that? Just a very general overview. Thanks!

Also, my trial is about to expire in 1 day and 8 hours. When I try to extend it for another 15 days, I get a vague error and no change in expiration. I did stop the array first. Not a great experience the problems started =/

Unfortunately, the same thing happens when booting in safe mode. Also, none of the containers seem to be the cause. To make matters worse, every time I reboot, the system fails to start properly and I can't access the webui. I have to do a physical reset, and then it starts normally (although the same Docker issue remains). None of this was happening after install. At this point, should I just start over? What is the best way to reset the system without losing data?

Sorry for the delayed response. Busy weekend. That’s what I thought, which is why it doesn’t make much sense. It also wasn’t happening right after deploying the containers for the first time. What could be causing the docker service to fail to start? Maybe I should try disabling the plugins. Could one of them be responsible? Or do you have any other debugging steps you’d recommend? Nothing out of the expected: Filesystem Size Used Avail Use% Mounted on rootfs 16G 915M 15G 6% /Thanks again for your help!

Yes, everything works fine when I do that, but only until the next reboot (whether I stop the array first or not). I've done this maybe half a dozen times. Got it. I’ve checked all the applications, and I don’t think any of them is causing this issue. Also, if I’m understanding correctly, this would show the used space inside the image with all the apps running, and it's well below 50GB: root@unraid:~# docker system df TYPE TOTAL ACTIVE SIZE RECLAIMABLE Images 43 43 16.83GB 542.2MB (3%) Containers 47 47 1.983GB 0B (0%) Local Volumes 3 3 0B 0B Build Cache 0 0 0B 0BIt’s not the end of the world if I never have to reboot, but when I do, it’s really inconvenient and frustrating. It feels like something’s broken = /

I don't think it is fiiling up, I was just testing different configurations for debugging. Checked mappings, all seems ok. Already did that many times. As I said, it works, but when rebooting (even if stopping array first), the problem always occurs again. Any more ideas? I already sent the diagnostics file, if that helps. Thanks for helping!

I'm currently on a trial and loving it! I’ll definitely be purchasing a license. However, I'm facing a strange issue. After every clean system reboot, the array starts up fine, but the Docker service fails to start. In the Docker tab, I see the message: "Docker Service failed to start." In the logs, I see the following: Oct 2 17:48:24 unraid rc.docker: Starting Docker daemon... Oct 2 17:48:25 unraid sysDrivers: SysDrivers Build Complete Oct 2 17:49:00 unraid rc.docker: Docker daemon... Failed. Oct 2 17:51:20 unraid webgui: docker stats error: Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running? If I recreate the Docker image as per the documentation, everything works fine again, but it's inconvenient to do this after every reboot or shutdown. I don't think this is caused by a corrupted docker image. Any ideas on how to fix this? unraid-diagnostics-20251002-1754.zip