mklecka

I'm planning to get one. But I thought docker cfg is stored on the USB, so why would it reset do default after a power loss?

Noone able to help me?

Hi, i've had some problems with docker not starting after power loss. The issue seems to be, that the docker settings get reset after power loss (to the dafult values, with Enable docker = no, disk size back to 20GB from my set 50GB etc.) If i enable it manually again, it starts no problem. Is there any way to eliminate this in the future? Thanks for any help. First diag right after boot and second after fixing the docker settings and starting the service. ghost-diagnostics-20240121-1229-after power loss.zip ghost-diagnostics-20240121-1232-changed back to my settings.zip

Hi, mount appdata to the original path "/home/app/.local/share/spoolman", start the container and if it shows permission error in the log run New Permissions from the "Tools" menu in unraid. That should fix it and database should be in the right place in appdata

Hi, i trying to resolve the permission issues on Spoolman github, but nothing so far. The workaround is manually changing permissions for the appdata folder created (i dont know why its created with wrong permissions). You can use the original path to the container data folder "/home/app/.local/share/spoolman" and manually change appdata folder permissions to this or run the new permissions tool from "Tools" tab in the unraid menu.

Hi, did you remove every variable you are not using? If you just want to use sqlite then basically remove everything except the path and port variables.

[Template only, I am not the container author/maintainer] Template: https://github.com/m-klecka/unraid-templates/blob/main/spoolman/spoolman.xml Source container: https://github.com/Donkie/Spoolman Spoolman is a docker application with Klipper support for tracking filament spool usage. I'll try to provide support for the template here, but any issues with the container should be posted to the creator's github repo The default data path inside container has problem with unraid appdata permissions. After installing open unraid console and run "sudo chown -R 1000:1000 /mnt/user/appdata/spoolman" (or your different specified appdata path) to fix the issue.

That worked:) Many thanks for helping

I guess it worked, but when i now try to format, it still says unmountable. Heres another diag. ghost-diagnostics-20230710-1218.zip

Tries that like 5 times, but heres another diag after reboot and format. ghost-diagnostics-20230710-1143.zip

Here ghost-diagnostics-20230710-1136.zip

Hi, i'm unable to mount a new cache drive. I cant erase/format it either. It was previously used as a proxmox drive. Tried restarting, unassigning etc. Any tips? Thanks ghost-diagnostics-20230710-1054.zip

yes, first list is containers on br0 network which are all accessible when NPM container starts. second are containers on custom network (in my case dockernet) which i can't reach until i completely restart docker. yeah, i could do that. I just really dont understand, why my setup only works after docker restart.. Other than that, i have no problems with it. And i use custom network so containers can communicate just by container name.

ok, so me again.. i thought it was long container loading times, but problem still presists as its is about 20 mins from unraid start and its still not working. Here's a list to see better whats accesible. br0, custom ip - can access though IP and NPM NPM UI Home asssitant VM Router Adguard home custom docker network - can't access via NPM, but can through IP:port sonarr radarr homepage jellyfin jellyseer etc etc unraid ui - cant access through NPM but can through IP Again, if i disable docker in unraid and reenable it, then everything loads through NPM no problem. Thanks for any help.

sorry to waste your time, im fkin dumb.. didnt occur to me, that some containers take really long time for me to start and werent started yet..