New Install - init-stage2 failed - changing ownership not permitted on logs folder

Checklist

• Have you pulled and found the error with jc21/nginx-proxy-manager:latest docker image?
  • Yes
• Are you sure you're not using someone else's docker image?
  • Yes
• Have you searched for similar issues (both open and closed)?
  • Yes

Describe the bug
After an update of the docker image the init did fail (see below). So I created a new container.

1. start container
2. "logs" folder in "data" is created successfully
3. error as shown here in the log:

[s6-init] making user provided files available at /var/run/s6/etc...exited 0.
[s6-init] ensuring user provided files have correct perms...exited 0.
[fix-attrs.d] applying ownership & permissions fixes...
[fix-attrs.d] done.
[cont-init.d] executing container initialization scripts...
[cont-init.d] 01_perms.sh: executing... 
Changing ownership of /data/logs to 0:0
chown: changing ownership of '/data/logs': Operation not permitted
[cont-init.d] 01_perms.sh: exited 1.
!!!!!
 init-stage2 failed.
!!!!!

Nginx Proxy Manager Version
2.9.5 - pulled jc21/nginx-proxy-manager:latest today

Operating System
Portainer LXC on Proxmox server (x64)
Maybe important detail: Mapped folders for data etc. are on an NFS Share.

Start with the container's 01_perms.sh initialization step and reproduce the failure using the jc21/nginx-proxy-manager:latest image with /data/logs on an NFS share. Compare the initialization behavior with a local data folder and verify that a new container completes init-stage2 without the ownership error.