Unbound + Pihole in separate containers

[AirAlarm]

Describe the bug
Hello, I have installed the unbound container as per manual, config files were placed to the mounted directory.
An already existing "pihole_default" network was set for the unbound container in the Portainer.
In Portainer on the console of the unbound container I'm getting an error message
[1730831636] unbound[1:0] warning: unbound is already running as pid 1.

Set Pihole to 192.168.50.18:5335 Upstream DNS, answers with N/A and the google.com in this case would not load.

To Reproduce
Steps to reproduce the behavior:

1. Docker run command
   sudo docker run
   --name=unbound-rpi
   --volume=/srv/dev-disk-by-uuid/Config/unbound:/opt/unbound/etc/unbound/
   --publish=5335:53/udp
   --publish=5335:53/tcp
   --restart=unless-stopped
   --detach=true
   mvance/unbound-rpi:latest

2. Config files
   https://github.com/MatthewVance/unbound-docker-rpi/tree/master/1.19.2/data/opt/unbound/etc/unbound

3. Directory structure
   

Error messages
[1730831636] unbound[1:0] warning: unbound is already running as pid 1.