linuxserver / docker-radarr

GNU General Public License v3.0
646 stars 104 forks source link

Permissions issue in latest branch #127

Closed RWatson0412 closed 3 years ago

RWatson0412 commented 3 years ago

linuxserver.io

When trying to import by movies library, I would consistently receive the following error:

2020-12-29 15:21:50.2|Trace|DiskProviderBase|Directory '/movies/' isn't writable. Access to the path '/movies/radarr_write_test.txt' is denied.
2020-12-29 15:21:51.0|Trace|RadarrErrorPipeline|Handling Exception
2020-12-29 15:21:51.0|Warn|RadarrErrorPipeline|Invalid request Validation failed:
 -- Path: Folder is not writable by user abc

This was despite the fact that I had thoroughly checked file permissions up to and including manually logging in with the abc and creating the file in the /movies directory myself.

I was able to resolve this issue for myself by switching from the latest to the nightly tag which worked immediately with no other changes made between tests.


Expected Behavior

Media imports when directory is selected.

Current Behavior

Unexpected and unexplained file permissions errors.

Steps to Reproduce

  1. Create container using latest tag.
  2. Connect via web client.
  3. Import movies.
  4. Error occurs.

Environment

OS: Docker on Arch CPU architecture: x86_64 How docker service was installed: ghcr.io/linuxserver/radarr:latest pulled with docker-compose.

Command used to create docker container (run/create/compose/screenshot)

Relevant Docker-Compose Section:

   radarr:
      image: ghcr.io/linuxserver/radarr:nightly
      container_name: radarr
      security_opt:
         - no-new-privileges:true
      networks:
         - network
      environment:
         - PUID=1000
         - PGID=1000
         - TZ=$TZ
         - UMASK_SET=022
      volumes:
         - /mnt/share/Downloads:/downloads
         - /mnt/share/Movies:/movies
         - /home/username/docker/radarr:/config
      ports:
         - 7878:7878
      restart: unless-stopped
github-actions[bot] commented 3 years ago

Thanks for opening your first issue here! Be sure to follow the issue template!

github-actions[bot] commented 3 years ago

This issue has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs. Thank you for your contributions.

homerr commented 3 years ago

This was taken from the nightly build - and given we're going way back here and no other report of this issue I'm going to close this.