SnugglyDino

How do I fix this error when installing a docker container? What does it mean? docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/mnt/user/appdata/postgresql_alpine" to rootfs at "/var/lib/postgresql/data": change mount propagation through procfd: open o_path procfd: open /var/lib/docker/btrfs/subvolumes/93598d4db74bc40f1c319adf4ada747e78f880d725d690e63d36c8c4cb73c9e5/var/lib/postgresql/data: no such file or directory: unknown. Not sure if it's related but I recently converted my Docker Service, Docker data-root from "btrfs vDisk" to "Directory". I can install other Apps from the community store just fine. Attached Diagnostics just incase that helps and below is all the info I have from the docker install. There are no other logs that I'm aware of. docker run -d --name='PostgreSQL_Alpine' --net='dinopark' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="FossilTower" -e HOST_CONTAINERNAME="PostgreSQL_Alpine" -e 'POSTGRES_DB'='postgres' -e 'POSTGRES_USER'='postgres' -e 'POSTGRES_PASSWORD'='postgres' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='' -p '5432:5432/tcp' -v '/mnt/user/appdata/postgresql_alpine':'/var/lib/postgresql/data':'rw' --user=99:100 --memory=2G --restart=unless-stopped 'postgres:alpine' WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. 78493e6f64fb7919b98a4349bdc5ee164b1f762653aa8a0db2a50188bd39c0ad docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/mnt/user/appdata/postgresql_alpine" to rootfs at "/var/lib/postgresql/data": change mount propagation through procfd: open o_path procfd: open /var/lib/docker/btrfs/subvolumes/93598d4db74bc40f1c319adf4ada747e78f880d725d690e63d36c8c4cb73c9e5/var/lib/postgresql/data: no such file or directory: unknown. The command failed. fossiltower-diagnostics-20251028-1727.zip

How can I tell which one is active? I'm assuming the one on the Cache drive is the one I am using but is there any way to double check? Or do I just have to delete the one on Disk 1 (after downloading the file for backup) and hope for the best?

Looks like the only thing in there is a docker.img file. Stopped the docker service and VM service. Ran the mover again with mover logging enabled. The docker.img file refuses to budge. Attached is the updated diagnostics. fossiltower-diagnostics-20251028-1443.zip

How do I get the system share off of disk1? I thought following the steps here (https://forums.unraid.net/topic/120220-fix-common-problems-more-information/?tab=comments#comment-1098683) would take all my system shares off of disk 1 and onto my cache.

The main reason I started poking around for things wrong with my Unraid server in general is because I keep getting the same error when I try to install/run PostgreSQL_Alpine and cannot figure out how to fix it. docker run -d --name='PostgreSQL_Alpine' --net='dinopark' --pids-limit 2048 -e TZ="America/Los_Angeles" -e HOST_OS="Unraid" -e HOST_HOSTNAME="FossilTower" -e HOST_CONTAINERNAME="PostgreSQL_Alpine" -e 'POSTGRES_DB'='postgres' -e 'POSTGRES_USER'='postgres' -e 'POSTGRES_PASSWORD'='postgres' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.icon='' -p '5432:5432/tcp' -v '/mnt/cache/appdata/postgresql_alpine':'/var/lib/postgresql/data':'rw' --user=99:100 --memory=2G --restart=unless-stopped 'postgres:alpine' WARNING: Your kernel does not support swap limit capabilities or the cgroup is not mounted. Memory limited without swap. cb5a7a7e0206cc37227a6d75e50ec02c16c3158de74aec4e115300e4edb3090f docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: error during container init: error mounting "/mnt/cache/appdata/postgresql_alpine" to rootfs at "/var/lib/postgresql/data": change mount propagation through procfd: open o_path procfd: open /var/lib/docker/btrfs/subvolumes/0f5abc07d057f62fa3844b35cde2d395159746f4ef38822f226b2134c26781cc/var/lib/postgresql/data: no such file or directory: unknown. The command failed.

The reason for changing my settings share from Cache + Array to Cache only is that I recently converted my Docker data-root from "btrfs vDisk" to "Directory" and in the more information Unraid states "You must specify a folder for Docker. The system will automatically create this folder when the Docker service is first started. It is recommended to create this folder under a share which resides on the Cache pool (setting: cache=Only). For best performance SSD devices are preferred."

How can I fix "Share system set to cache-only, but files / folders exist on the array... You should change the shares settings appropriately or use the dolphin / krusader docker applications to move the offending files accordingly. Note that there are some valid use cases for a set up like this. In particular: THIS More Information"? I followed @Squid 's steps found on his post back in 2022 (https://forums.unraid.net/topic/120220-fix-common-problems-more-information/?tab=comments#comment-1098683). Changed the "Secondary Storage" from "none" to "Array". Set the mover to "Array -> Cache" and then ran the mover. Then realized I forgot to stop my Docker containers and VMs. So I went into my Unraid Settings turned off Docker and VM and then ran the mover again multiple times. Changed the "Secondary Storage" back to "none". Still got the same error. Restarted my server. Still got the same error. Tried all the steps one more time. Still got the same error. Even ran the mover with "Secondary Storage" set to "none" just in case. No change. What am I doing wrong here? I've attached to Diagnostic files to help with debugging. fossiltower-diagnostics-20251028-1229.zip

Sounds good. I'll return it to default. Thank you for all your help. Now I can go back to enjoying the rabbit hole that is the Community Apps hahaha. Also if you got any other words of wisdom, I would love to hear it! Even if it is off topic for this thread now.

Oh looks like I have that going to. Don't remember setting it up lol.

You make a very good point. How do I backup to an off server location? Unrelated to backups. But do you have a recommendation for Mover settings/schedule?

My license key is tied to my Unraid.net account. And this is probably a big no no but I just have everything being backed up to the server itself

deleted Steps followed. Looks like everything is the way it should be. I attached the diagnostics as well. jurassicpark-diagnostics-20250206-0310.zip

You are 100% right. 1.5TB was a bad choice. So I did change it but wanted to play things a bit safe. So I set it to 100G

I just did a "compute all" instead. Figured it would be more insightful. Hopefully that's ok.

Sorry for my slow response. It has been another busy day and I cannot get to my hobbies as quickly as I like to more often than not. So I have not read your most recent 3 comments. Before I do I wanted to give you a server update. It looks like good news. My server has successfully freed up my entire cache drive (see pic). The bad news. I have no idea why. I have attached a new diagnostics file in case it can provide any insight on what changed since last night. jurassicpark-diagnostics-20250206-0117.zip

That makes more sense now. Thank you.

Correction. Mover has just finished. But this is very interesting. Either I don't understand that "Minimum free space" setting, or mover did not work right. Because it finished moving files and I don't have 1.5TB of Free cache jurassicpark-diagnostics-20250205-0400.zip

The mover is still running. Will probably have to update with new diagnostics data in the morning. But it looks like it is working. Cache Used has already dropped to 1.41 TB. Ahhh I think I get "Minimum Free Space" setting inside the cache drive now. It only took me reading and rereading your description and Unraid's description like 10 times each. I was getting confused because you were talking in terms of "Files". While Unraid talks in terms of "Volume". You are both saying the same thing but slightly differently. If I understand it correctly, The "Minimum free space" setting is telling Unraid how much Free Space I want on my cache drive. That means if the remaining free space on my cache drive ever becomes less than this amount, so in my case less than 1.5 TB (ex: 1.4TB), then the mover will activate and start moving files off the Cache (like it is currently doing) until the remaining free space becomes 1.5 TB or larger. You talk about this setting in terms of File size because I never want Unraid to run into a situation where it cannot completely write a file onto a drive and cause an error. So you recommend to set the remaining free space to never drop below the largest individual file size that I might encounter. That way I maximize using my cache drive while never encountering a write error. Hopefully that explanation makes sense for future people. Now I mostly understand why you said 50G. My only remaining question is why you said "50G" (53,687,091,200) instead of "50 GB" (50,000,000,000)? Also does the space between the number and letter matter?

What is a good way to figure that out? I have plex writing to Cache. Since it's a 2TB drive so maybe 1.5TB? Something also that just popped into my head. Does Unraid have some sort of Trash Can or Recycling feature? I just remember I have a Docker Application called Maintainerr. It's supposed to clean up unwatched Plex movies and tv shows (that is what is in the d - - a (aka data) folder). I was running out of space on my system so I accelerated the clean up process and it recently deleted about 10TB of files. Could that some how effect the cache drive? I activated mover and will attach the new diagnostics data once it is finished

I logged into my Unraid server to mess around with some new Docker containers when I noticed my cache drive was very very full. 1.97 TB out of 2 TB used with only 27.8 GB free. I am assuming being that full cannot be a good thing. Tried to do some Googling but it seems like all the solutions are specific to and diagnostics logs. Which makes sense, but makes it difficult for me to troubleshoot on my own since I don't know how to read and understand the diagnostic files. Would someone be able to use my cache problem to explain to me how to read the diagnostic files. I am hoping to learn from this experience so next time I might be able to figure out the solution to my next problem on my own. Attached are my anonymized Diagnostic logs. jurassicpark-diagnostics-20250204-0258.zip

You are right. Thank you for that clarification. Changing the network to a bridge that shares the same IP as my host system fixed the problem. How can I manually set the IP address for Node Red if I want to put it on a network that's on a different VLAN? I want it on the same network as my Home Assistant VM. You said I have to do it in the settings of the application itself. Where is this setting in Node Red? Is there really no way to set it from the container setup?

@Skylord123 Would you be able to send a picture of your setup file so I can copy it? Is there anything different?

I'm confused can you please elaborate. Why would changing the port to 1881 in the Port field of the Docker Setup up not change the port value from 1880 to 1881? I've done that with countless other containers and it has worked just fine. I changed it to not conflict with Nginx Proxy Manager but I really didn't need to since NPM runs on a different VLAN now that I'm thinking about it. Changing the port value back to the default 1880 in the Docker Setup unfortunately does not fix anything either (see pictures).

Looking to get an HL15 for my next chassis and need to figure out the best way to add HDD for my novice setup. My motherboard is a MSI MAG B660 Tomahawk with a 12th Gen Intel i5. I'm not sure if I should be getting a HBA card or some sort of PCIe to Sata expander. Right now this is what I'm eyeing up on amazon... 1.) PCIe x1 to 12-Port SATA3.0 Expansion Card,6Gbps SATA Adapter for SSD/HDD, Plug and Play with 12 Status LEDs, Compatible with Windows/Linux/Ubuntu/ESXi/Synology NAS 2.) PCIe Sata Expansion Card M.2 to SATA3.0 Adapter Card, 6Gbps High Speed Sata Expansion Card, ASM1166 M.2 PCIE to SATA Expansion Card with Smart Indicator, M.2 Sata Adapter 3.) LSI Logic Controller Card 05-25600-00 9300-16i 16Port 12Gb/s SAS x8 PCI-Express 3 Full Height Brown Box Which option do you recommend I pick or just tell me while all these options are wrong. I'm mainly looking for low power consumption and being able to connect all 15 hard drive slots on the HL15. Speed is 3rd.

Looking to get an HL15 for my next chassis and need to figure out the best way to add HDD for my novice setup. My motherboard is a MSI MAG B660 Tomahawk with a 12th Gen Intel i5. I'm not sure if I should be getting a HBA card or some sort of PCIe to Sata expander. Right now this is what I'm eyeing up on amazon... 1.) PCIe x1 to 12-Port SATA3.0 Expansion Card,6Gbps SATA Adapter for SSD/HDD, Plug and Play with 12 Status LEDs, Compatible with Windows/Linux/Ubuntu/ESXi/Synology NAS 2.) PCIe Sata Expansion Card M.2 to SATA3.0 Adapter Card, 6Gbps High Speed Sata Expansion Card, ASM1166 M.2 PCIE to SATA Expansion Card with Smart Indicator, M.2 Sata Adapter 3.) LSI Logic Controller Card 05-25600-00 9300-16i 16Port 12Gb/s SAS x8 PCI-Express 3 Full Height Brown Box Which option do you recommend I pick or just tell me while all these options are wrong. I'm mainly looking for low power consumption and being able to connect all 15 hard drive slots on the HL15. Speed is 3rd.