Open fahadshery opened 2 months ago
Thanks for opening your first issue here! Be sure to follow the relevant issue templates, or risk having this issue marked as invalid.
I can also write to the /movies folder from INSIDE the container.
You're likely exec'ing into the container as root, but radarr runs as user abc
inside, which is mapped to the PUID/PGID
you set in docker arguments
You're likely exec'ing into the container as root, but radarr runs as user
abc
inside, which is mapped to thePUID/PGID
you set in docker arguments
Yes and that PUID
and PGID
is mapped to my user which can read/write/execute in the /movies
folder.
Here is how I am mounting the cifs share:
//192.168.10.90/media /mnt/nas/media cifs uid=1000,gid=1000,credentials=/home/myuser/.smbcreds 0 0
I am having same exact issue. everything still works, adding new movies, importing from download client, literally everything besides seeing root folders and importing movies manually, ive tried downgrading versions the past few weeks, and still the same. I can delete movies still from the ui. I only set up this VM about 6 weeks ago and everything was fine then. I guess i havent tried to manually import since then so I'm not sure when it started.
My fstab for mounting:
//ip/share-name/Media /data/media cifs username=username,password=password,uid=1000,gid=1000,auto,nofail 0 0
Ive tried re-running some permissions commands:
sudo chown -R $USER:$USER /data
sudo chmod -R a=,a+rX,u+w,g+w /data
My PUID/PGID are set same as above docker compose. I'm just mapping /data:/data
I am getting the same exact error message as well.
Docker version 26.0.1, build d260a54 Ubuntu 22.04.4
EDIT: Updated to Ubuntu 24 with docker version 26.1.0 and its fixd
I have also encountered this issue. Updating to Ubuntu 24 and docker 26.1.0 like mentioned by Mafyuh above, did not work for me. The only way I managed to get this to work was to set both PUID and PGID to 0.
That means you have permissions issues, which you're bypassing by having radarr run as root, which we neither recommend, or support.
This issue has been automatically marked as stale because it has not had recent activity. This might be due to missing feedback from OP. It will be closed if no further activity occurs. Thank you for your contributions.
Is there an existing issue for this?
Current Behavior
I can see all my movies INSIDE the container. I can also
write
to the/movies
folder from INSIDE the container. But I am unable to import my existing movies. I have been using the same movies folder for few years without any issues. This is what I see:and this is the error I see when try and import:
Expected Behavior
Being able to import my existing movies.
Steps To Reproduce
Just spin up the docker and portainer. Then setup using docker compose
Environment
CPU architecture
x86-64
Docker creation
Container logs