-
some Docker Containers dont start anymore
Thats it. Thank You. I'v temporary set the limit down to 100GB and recreating all Containers now. Is there a reason why the limit counts on the single Disks and not on the Array Size? Beacause thats what I was thinking. Also Thank You @JorgeB for your Answer.
-
some Docker Containers dont start anymore
I've deleted the /mnt/user/system/docker/docker.img via Settings and recreated one single container -> same Problem. I'm really out of Ideas here. Something is totally screwed up.
-
some Docker Containers dont start anymore
So I've searched and tried a little more but nothing helped. The Docker vDisk Size is set to the 20GB default and my Containers are only using 11.9GB in total. Even if I increase this to 30GB nothing changes. Ive also tried to delete some containers and recreated it from the "previous Apps" Section but they still complain about not enough disk space.
-
ErrPunktErr changed their profile photo
-
ErrPunktErr started following some Docker Containers dont start anymore
-
some Docker Containers dont start anymore
Hey everyone, out of the blue I have a Problem with some Docker Containers. I was updating some plugins in Homeassistant and needed to restart the service (inside the Container) but it never came back up. So I decided to restart the Container itself and even it shos "running" in Unraid, it is not reachable via Web Interface. The log tells me "OSError: [Errno 28] No space left on device: '/config/home-assistant.log.fault'". So, because the Container itself does not collect any Data (not that much) and I have still plenty of Space (324 GB free in the array) I suspected a permissions Problem and ran Tools/NewPerms on all Disks but that did not help. I even rebooted the Unraid System but no luck. Paperless tells me: "sqlite3.OperationalError: unable to open database file" Jellyfin: "Microsoft.Data.Sqlite.SqliteException (0x80004005): SQLite Error 14: 'unable to open database file'." Audiobookshelf: "Error: ENOSPC: no space left on device, open '/metadata/logs/crash_logs.txt'" I have no clue whats going on here or where to start investigating. homeserver-diagnostics-20240406-1921.zip