February 13, 20251 yr I just got this error... ...and I'm not sure how to fix it. I looked at the folder it mentions and it appears wide open... ...this container has been writing to/from /media/Media for YEARS and, all of a sudden, this. I'm baffled. /media/Media permissions look exactly the same as .../complete/tv... The Docker container is FileBot, which I've used to rename and move files on the server for literally years and it's never had any kind of permissions issue. I just moved a bunch of files from one directory to a new directory (moved my media libraries from /media/Media/downloads/ to /media/Media/data as the trash guide says...trying to get my paths all sorted out so the Arrs are finally happy...) and now FileBot is angry. Anything to look at, any words of wisdom, any help at all is greatly appreciated. Thank you!!
February 13, 20251 yr Community Expert 3 minutes ago, rmp5s said: /media/Media/downloads/ to /media/Media/data These are not valid host paths on Unraid. Are you talking about the container paths? Post docker run.
February 13, 20251 yr Author 5 minutes ago, trurl said: These are not valid host paths on Unraid. Are you talking about the container paths? Post docker run. The paths are just IN the container itself. It's reading, manipulating and writing data back to the array. Can't post that right now as the server decided to crash. Which is a fun, new trick it's learned...
February 13, 20251 yr Community Expert You can go directly to the correct support thread for this container by clicking its icon in the Unraid webUI and selecting Support.
February 13, 20251 yr Community Expert Post docker run when you get rebooted. Then we can check permissions using the host paths.
February 13, 20251 yr Author 9 minutes ago, trurl said: Post docker run when you get rebooted. Then we can check permissions using the host paths. This looks craaaaaaaaazy...I don't remember EVER seeing a "docker run" look like this. lol docker run -d --name='FileBot' --net='bridge' --pids-limit 2048 -e TZ="America" -e HOST_OS="Unraid" -e HOST_HOSTNAME="" -e HOST_CONTAINERNAME="FileBot" -e 'OPENSUBTITLES_USERNAME'='' -e 'OPENSUBTITLES_PASSWORD'='' -e 'AMC_INTERVAL'='1800' -e 'AMC_INPUT_STABLE_TIME'='10' -e 'AMC_ACTION'='test' -e 'AMC_CONFLICT'='auto' -e 'AMC_MATCH_MODE'='opportunistic' -e 'AMC_ARTWORK'='n' -e 'AMC_MUSIC_FORMAT'='{plex}' -e 'AMC_MOVIE_FORMAT'='{plex}' -e 'AMC_SERIES_FORMAT'='{plex}' -e 'AMC_ANIME_FORMAT'='{plex}' -e 'AMC_PROCESS_MUSIC'='y' -e 'AMC_SUBTITLE_LANG'='' -e 'AMC_LANG'='English' -e 'USER_ID'='99' -e 'GROUP_ID'='100' -e 'UMASK'='000' -e 'APP_NICENESS'='' -e 'DISPLAY_WIDTH'='1280' -e 'DISPLAY_HEIGHT'='768' -e 'SECURE_CONNECTION'='0' -e 'X11VNC_EXTRA_OPTS'='' -e 'FILEBOT_CUSTOM_OPTIONS'='' -e 'AMC_CUSTOM_OPTIONS'='' -e 'AMC_INPUT_DIR'='/watch' -e 'AMC_OUTPUT_DIR'='/output' -e 'AMC_INSTALL_PKGS'='' -e 'USE_FILEBOT_BETA'='0' -l net.unraid.docker.managed=dockerman -l net.unraid.docker.webui='http://[IP]:[PORT:]' -l net.unraid.docker.icon='https://raw.githubusercontent.com/jlesage/docker-templates/master/jlesage/images/filebot-icon.png' -p '7813:5800/tcp' -p '7913:5900/tcp' -v '/mnt/user/':'/storage':'rw' -v '/mnt/user/Media/':'/watch':'rw' -v '/mnt/user/Media/':'/output':'rw' -v '/mnt/user/appdata/FileBot':'/config':'rw' 'jlesage/filebot' e92befc3a113589805e73ce76861e281566ab7e0b The command finished successfully! It looks like it's setting rw permissions at the end...still doesn't work, though...hmm... Edited February 13, 20251 yr by rmp5s
February 13, 20251 yr Community Expert The only container paths I see there are /storage, /watch, /output, and /config. /media/Media paths would be inside docker.img, which are inaccessible to krusader or anything else, and could also fill docker.img 22 minutes ago, rmp5s said: the server decided to crash On the other hand, if you do have some container writing to invalid host paths, that might fill rootfs, and could cause all sorts of things including "crash". Do you understand docker volume mapping?
February 13, 20251 yr Author 9 minutes ago, trurl said: The only container paths I see there are /storage, /watch, /output, and /config. /media/Media paths would be inside docker.img, which are inaccessible to krusader or anything else, and could also fill docker.img On the other hand, if you do have some container writing to invalid host paths, that might fill rootfs, and could cause all sorts of things including "crash". Do you understand docker volume mapping? Right..."/watch" and "/output" are both mapped as the paths I need, /media/Media...that appears correct. That's where the data that the container uses is located. Yes, I understand volume mapping.
February 13, 20251 yr Community Expert 11 minutes ago, rmp5s said: /media/Media...that appears correc The container has no volume mappings for those paths.
February 13, 20251 yr Author 39 minutes ago, trurl said: The container has no volume mappings for those paths. Hmmm...going to have to look into this more in a bit...gotta get some work done. Thanks for the help.
February 15, 20251 yr Author Turns out I DID have the mappings correct. The issue was something with the way the destination path was entered in FileBot. I don't know why, because it looks the same to me, but I went in and entered the destination paths again and it works. Doesn't make a whole lot of sense, but hey...at least it works. I guess. Thanks for all the help!!
February 15, 20251 yr Community Expert If the new destination paths you entered started with /output that would make perfect sense.
February 15, 20251 yr Author 10 minutes ago, trurl said: If the new destination paths you entered started with /output that would make perfect sense. True true. But... storage/Media/data/usenet/complete/... ...just like the Trash Guide said is what I put in FileBot. Put it in again, literally watched and didn't see anything change, but now it's happy. Not sure. Pretty weird. May be a "refresh" kind of thing...that's all I can think of. Thank you for all the help!! Edited February 15, 20251 yr by rmp5s
February 15, 20251 yr Community Expert /storage in the container is /mnt/user on the host, your user shares. /media in the container is unknown to the host.
Join the conversation
You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.