s6-rc: warning: unable to start service prepare

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 update to 2.10.1 i got a error, if i use a custom ssl-ciphers file.

Log:
[+] Running 1/1
✔ Container nginx-proxy-manager Recreated 0.2s
Attaching to nginx-proxy-manager
nginx-proxy-manager | s6-rc: info: service s6rc-oneshot-runner: starting
nginx-proxy-manager | s6-rc: info: service s6rc-oneshot-runner successfully started
nginx-proxy-manager | s6-rc: info: service fix-attrs: starting
nginx-proxy-manager | s6-rc: info: service fix-attrs successfully started
nginx-proxy-manager | s6-rc: info: service legacy-cont-init: starting
nginx-proxy-manager | s6-rc: info: service legacy-cont-init successfully started
nginx-proxy-manager | s6-rc: info: service prepare: starting
nginx-proxy-manager | ❯ Configuring npmuser ...
nginx-proxy-manager | id: 'npmuser': no such user
nginx-proxy-manager | ❯ Checking paths ...
nginx-proxy-manager | ❯ Setting ownership ...
nginx-proxy-manager | ❯ Dynamic resolvers ...
nginx-proxy-manager | ❯ IPv6 ...
nginx-proxy-manager | Enabling IPV6 in hosts in: /etc/nginx/conf.d
nginx-proxy-manager | - /etc/nginx/conf.d/production.conf
nginx-proxy-manager | - /etc/nginx/conf.d/include/ssl-ciphers.conf
nginx-proxy-manager | sed: cannot rename /etc/nginx/conf.d/include/sedXg1RRw: Device or resource busy
nginx-proxy-manager | s6-rc: warning: unable to start service prepare: command exited 4
nginx-proxy-manager | /run/s6/basedir/scripts/rc.init: warning: s6-rc failed to properly bring all the services up! Check your logs (in /run/uncaught-logs/current if you have in-container logging) for more information.

Nginx Proxy Manager Version
2.10.1

To Reproduce
Steps to reproduce the behavior:

1. Add ssl-ciphers.conf to docker-compose.yaml
2. Start Container
3. See error

Expected behavior
A clean start without an error.

Operating System
Debian 11.x

Reproduce the failure using docker-compose.yaml with a mounted ssl-ciphers.conf, then inspect the prepare service output and the files under /etc/nginx/conf.d/include/. Focus on why sed cannot rename the mounted file; done means the container starts cleanly with the custom cipher configuration.