thomaslc66

Hello, Have you been able to find the root cause of your issue? I'm having the same problem. I think the key was not the issue because it was working for more than 3 years with the old, but still I replaced the key and I'm still experiencing the same issue every month, maybe. Thanks for your help.

Hello, I have this error on my unraid server: "Default docker appdata location is not a cache-only share". 100% true and 100% understood why, as I have my appdata set to cache for primary and array for secondary. Unraid documentation says that cache is for temporary speed read-write access and array is for longer storage. Then I searched for the error here on the forum and saw people say that people with this error need to: stop docker, change the move action for app data from Array -> Cache, and then put None in the second Storage. I do understand speed and everything. But I mean, my cache is 512 GB and I don't see the point of having all my data on it. Plus I have some docker containers like Unraid that store a lot of my personal data and having all of that on the Cache is a bit counter productive. My question is: "How would I keep my first array to be the cache but then, move my personal data or everything a bit bigger in size to the array, without seeing this error that my appdata is not cache-only" Thank you for the answer.

Have a look here, this might help you. https://medium.com/@the.virtual.samourai/unraid-rclone-plex-and-plex-debrid-eb70e7540fc5

I've been running two same container first one 97596.... was created through GUI. ( NOT WORKING ) second one d443b.... was created through command line. ( WORKING ) i think the problem comes from the COMMAND, the GUI created container add ubuntu at the end of the command. Why those unraid do that and how can i change this ? Is it possible for somebody if it's only me or this behaviour is the same on all unraid 6.7.2 ? Thanks

if docker is stopping this would impact my other container ? Because all my other container are started and doesn't seems to be impacted, no reboot. plus when i start a new docker container all from the command line, this container is running.

I've edited the template with GUI, hit apply. Then this widows shows, and nothing else. But when i try to start, still nothing. No log, even with the command "docker logs ubuntu" nothing. The only news is that now it shows Before it was showign uptime. Syslog are showing this: Really wierd. No clue what's happening. Thanks for your answer by the way

Hello, i'm quite new to unraid, but know a bit how docker works. I wanted to use clean docker image so i installed the community plugin and enabled the docker hub search option. I've set my docker settings like this: Then i downloaded a ubuntu image from docker hub. What i've tried was first to use bridge for network opening port 22 on container mapping it to a custom port on the host. Then using custom br0 mapping port 22 also too custom port. And at the end setting network to none and adding extra parameters to --network br0 But none of those parameters let me start the container. When i click on start the container try to start and then stop. (here you can see up time = 1 sec) Log is totally empty. Really need help on this, as i don't know why could cause this behavior. Docker is working as my other app in bridge is working fine. But even with bridge the docker container from docker hub is not booting up. Thank you in advance for all your future advice and time. Maybe someone already experienced this behavior. Unraid 6.7.2 Basic