PermissionError on /etc/letsencrypt/live/

[AgainstAllGood]

Error in jc21/nginx-proxy-manager:latest
Describe the bug
When i want to create a SSL Certificate in the frontent I get following error:

Error: Command failed: certbot certonly --config "/etc/letsencrypt.ini" --cert-name "npm-10" --agree-tos --authenticator webroot --email "a.pernkopf@aikq.at" --preferred-challenges "dns,http" --domains "owncloud.mydomain.example" 
Saving debug log to /var/log/letsencrypt/letsencrypt.log
An unexpected error occurred:
PermissionError: [Errno 1] Operation not permitted: '../../archive/npm-10/cert1.pem' -> '/etc/letsencrypt/live/npm-10/cert.pem'
Ask for help or search for solutions at https://community.letsencrypt.org. See the logfile /var/log/letsencrypt/letsencrypt.log or re-run Certbot with -v for more details.

at ChildProcess.exithandler (node:child_process:399:12)
at ChildProcess.emit (node:events:526:28)
at maybeClose (node:internal/child_process:1092:16)
at Process.ChildProcess._handle.onexit (node:internal/child_process:302:5)

Nginx Proxy Manager Version
v2.9.18

Additional context
I tried to chmod 755 /etc/letsencrypt/live/ with no avail
Docker-compose file:

version: '3'
services:
  app:
    container_name: "Nginx"
    image: 'jc21/nginx-proxy-manager:latest'
    restart: unless-stopped
    ports:
      - '80:80'
      - '81:81'
      - '443:443'
    volumes:
      - ./data:/data
      - ./letsencrypt:/etc/letsencrypt

[the1ts]

I think this is quite, simple, the npm docker container is trying to change permissions on ./letsencrypt/letsencrypt.ini and the permissions on the host aren't allowing it. This can happen with permission simple issues on the host side or having the letsencrypt directory on NFS setup wrongly to squash root access down to a user that doesn't have permission and many other reasons.
In short its a problem with where ./letsencrypt volume is being mounted from, not nginx proxy manager.

[poiNt3D]

I don't this it's a good practice trying to change permissions on a folder to root. A container should run with a user that has been given to it.
Particular pain is delivered by NFS shares, where the only option to permit changing ownership to root is mapping the entire share to root instead of a specific user created for that appliance.

[github-actions]

Issue is now considered stale. If you want to keep it open, please comment 👍

[github-actions]

Issue was closed due to inactivity.