Chown: changing folder ownership error - operation not permitted

[idojius86]

Hi,

I am trying to deploy your image, but I keep encountering a chown operation not permitted error when my data directory is hosted on an NFS share.

My Infrastructure:

• Hardware: Mini PC running Docker.
• Storage: Synology NAS mounted via NFS at /mnt/nas.
• Docker Mapping: The local path /mnt/nas is mapped to the internal container path /data.

Problem Description:

The container fails to start (or throws errors during initialization) because it attempts to perform a chown command on the paths defined in INCOMING_DIR and TEMP_DIR, which are located on the NFS mount. Since the NFS protocol restricts chown operations from remote clients, the process fails.

My Docker Compose configuration:

amule:
  container_name: amule
  image: ngosang/amule:latest
  environment:
    - PUID=1000
    - PGID=1000
    - GUI_PWD=secret
    - WEBUI_PWD=secret
    - MOD_AUTO_RESTART_ENABLED=true
    - MOD_AUTO_RESTART_CRON=0 6 * * *
    - INCOMING_DIR=/data/descargas/amule/completed
    - TEMP_DIR=/data/descargas/amule/temp
  ports:
    - "4711:4711"
    - "4712:4712"
    - "4662:4662"
    - "4665:4665/udp"
    - "4672:4672/udp"
  volumes:
    - /mnt/nas:/data
    - amule_data:/home/amule/.aMule
 
amule_data:
  driver: local

What I have already tried to solve this:

• Setting PUID and PGID correctly (1000).
• Running the container in privileged: true mode.
• Forcing the user via user: "1000:1000" in the docker-compose.
• Configuring the NFS mount on my host with no_root_squash.
• Manually setting permissions (chmod 777) and changing ownership on the physical folders in the Synology NAS.

Despite these attempts, the entrypoint script or the application itself still triggers a "chown" operation which is rejected by the filesystem. Do you have any recommendations for handling external mounts (like NFS/SMB) that don't support permission changes?

Thanks for your help and best regards!