Cannot append customizations to the provided Unbound configuration

[Thewansingh]

Cannot append customizations to the provided Unbound configuration

My container self updates every night, however on the latest release 1.19.2 my container was not being assigned an ip address. I decided to nuke that container and recreate a new one using this command. I also nuked my unbound config files folder and created a new empty one so i can edit and appened the provided unbound config files.

So i run docker run --name=unbound-rpi \ --volume=/my-directory/unbound:/opt/unbound/etc/unbound/ \ #i did add my own directory, this is just the base example --publish=53:53/tcp \ --publish=53:53/udp \ --restart=unless-stopped \ --detach=true \ mvance/unbound-rpi:latest

Now 2 things happend

• I cannot see the provided config files as i usually can to be able to config them
• My container is still not being assigned an ip (I'm running a custom bridge network, not the default docker bridge network)
• I also tried to create the container in the default bridge network, but still the same issue

[Nyurael]

My system is selfupdatding too and since this morning, unbound is down. Got the same problem, no IP anymore. Also, Container logs is full with:

[1710059707] unbound[1:0] warning: unbound is already running as pid 1. chown: cannot access '/opt/unbound/etc/unbound/unbound.log': No such file or directory

[MeCias]

I can confirm that. There are no IP addresses assigned any more. I tried all kind of network configurations. Nothing works.

[Klorins]

Same problem here too

[d-rez]

Potentially related to https://github.com/MatthewVance/unbound-docker-rpi/issues/51, the actual reason seems to be that the container crashes even with default config. Try rolling back to mvance/unbound-rpi:1.17.1

[Nyurael]

it should allready be fixed in the newest version