Console errors requesting access to block devices?

[RejectH0]

BUG DESCRIPTION
Upon launching unbound, the following error messages appear in the terminal console window:

unbound | cp: cannot create special file '/opt/unbound/etc/unbound/dev/random': Operation not permitted unbound | cp: cannot create special file '/opt/unbound/etc/unbound/dev/urandom': Operation not permitted unbound | cp: cannot create special file '/opt/unbound/etc/unbound/dev/null': Operation not permitted unbound | cp: cannot create special file '/opt/unbound/etc/unbound/dev/random': Operation not permitted unbound | cp: cannot create special file '/opt/unbound/etc/unbound/dev/urandom': Operation not permitted unbound | cp: cannot create special file '/opt/unbound/etc/unbound/dev/null': Operation not permitted

To Reproduce
Steps to reproduce the behavior:

1. Docker run command or compose file:
   'version: "3.3"
   services:
   unbound:
   container_name: unbound
   ports:
   • 5335:5335/tcp
   • 5335:5335/udp
     volumes:
   • ./etc-unbound:/opt/unbound/etc/unbound/
     restart: unless-stopped
     image: mvance/unbound:latest
     networks:
   • pihole_pihole_default
     networks:
     pihole_pihole_default:
     external: true
     '

Expected behavior
I was not aware that block devices are available to Docker containers.
I am new to Docker, so it could be something I'm doing wrong, but I can't find it and neither can ChatGPT-4.