unbound-docker-rpi 1.17.1 fails to start due to missing file unbound.log

[JEllgring]

Describe the bug
The container of unbound-docker-rpi, version 1.17.1 hangs in a restart loop after trying to start it.

The reason for this behaviour is the missing (compared to version 1.17.0) file data/opt/unbound/etc/unbound/unbound.log
in the source code.
Because of this, unbound.sh fails at line 376:
chown _unbound:_unbound /opt/unbound/etc/unbound/unbound.log && \

To Reproduce
Steps to reproduce the behavior:

1. Build the image from source
2. Run the container with
   docker run --name=unbound \ --publish=53:53/tcp \ --publish=53:53/udp \ --restart=unless-stopped \ --detach=true \ unbound-rpi64:1.17.1
3. Watch the container restarting with docker ps

Error messages
Output of docker logs unbound is

chown: cannot access '/opt/unbound/etc/unbound/unbound.log': No such file or directory
[1679170954] unbound[1:0] warning: unbound is already running as pid 1.
[1679170954] unbound[1:0] error: unable to open var/root.key for reading: No such file or directory
[1679170954] unbound[1:0] error: error reading auto-trust-anchor-file: var/root.key
[1679170954] unbound[1:0] error: validator: error in trustanchors config
[1679170954] unbound[1:0] error: validator: could not apply configuration settings.
[1679170954] unbound[1:0] error: module init for module validator failed
[1679170954] unbound[1:0] fatal error: failed to setup modules

Additional context
Solution:
Add a line to unbound.sh before the chown:
touch /opt/unbound/etc/unbound/unbound.log && \
chown _unbound:_unbound /opt/unbound/etc/unbound/unbound.log && \

[Gatsby-Lee]

@JEllgring thank you

[DrTuup]

I've found a temporary solution to this. You can mount a volume with your file to the container, just to make sure that it exists like this:
volumes: - "your/config/dir:/opt/unbound/etc/unbound/unbound.log"

Hope this helps.

[ajsobrino700]

@DrTuup your solution is good, the error is too in the version 1.19.2 @MatthewVance

[g0lg0-93]

Merry Christmas y'all.

I didn't know whether to create a separate issue to piggyback off this.

I experience the a permission issue with the logs. I've set the path to be the directory I've mapped for unbound.

Compose:
unbound: container_name: unbound image: mvance/unbound-rpi:latest #1.19.2 networks: dns_network: ipv4_address: 10.0.8.5 volumes: - ./unbound:/opt/unbound/etc/unbound ports: - "5053:53/tcp" - "5053:53/udp" restart: unless-stopped

snippet from unbound.conf (which was automatically generated from unbound.sh):
` # If you want to log to a file, use:
logfile: /opt/unbound/etc/unbound/log/unbound.log
# Set log location (using /dev/null further limits logging)
#logfile: /dev/null

# Set logging level
# Level 0: No verbosity, only errors.
# Level 1: Gives operational information.
# Level 2: Gives detailed operational information including short information per query.
# Level 3: Gives query level information, output per query.
# Level 4:  Gives algorithm level information.
# Level 5: Logs client identification for cache misses.
verbosity: 5`

No unbound.log file is automatically created. On another note, is it possible to set verbosity level to 2 & 5?

Thanks in advance