Use protocol In container without permission fault

[CamelT0E]

I would like to use the protocol in the unbound container. The external logging works without problems. But it's nice if you have a log in the container to make troubleshooting easier. Logging to /dev/stdout works without problems. However, there is always an error message due to write permissions: unbound[1:0] error: Could not open logfile /dev/stdout: Permission denied.

The problem affects all directories in /dev:

Can you fix the rights please? It is not unusual to use a log in the container.

Thanks

[tetafro]

Having the same issue. Tried 1.12.0 and 1.19.3.

Example

$ mkdir unbound
$ echo ' 
server:
  interface: 0.0.0.0
  access-control: 0.0.0.0/0 allow
  hide-identity: yes
  hide-version: yes
  logfile: /dev/stdout
  verbosity: 0
  local-zone: "home." static
  local-data: "example.home. IN A 192.168.1.1"
  local-data-ptr: "192.168.1.1 example.home"
forward-zone:
  name: "."
  forward-addr: 1.1.1.1
remote-control:
  control-enable: no
' > unbound/unbound.conf

$ docker run -d --rm -v $(pwd)/unbound:/opt/unbound/etc/unbound --name unbound mvance/unbound:1.19.3

$ docker logs unbound 
[1716789573] unbound[1:0] error: Could not open logfile /dev/stdout: Permission denied
[1716789573] unbound[1:0] info: start of service (unbound 1.19.3).