Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Several Errors in fresh UNRAID Docker install #116

Open
twitch86 opened this issue Nov 14, 2022 · 5 comments
Open

Several Errors in fresh UNRAID Docker install #116

twitch86 opened this issue Nov 14, 2022 · 5 comments

Comments

@twitch86
Copy link

Hi - with my fresh UNRAID install i get the following Logs with the Unbound Docker:

[1668439651] libunbound[22:0] error: udp connect failed: Cannot assign requested address for 2001:500:9f::42 port 53
[1668439651] libunbound[22:0] error: udp connect failed: Cannot assign requested address for 2001:dc3::35 port 53
[1668439651] unbound[1:0] warning: setrlimit: Operation not permitted
[1668439651] unbound[1:0] warning: cannot increase max open fds from 40960 to 57568
[1668439651] unbound[1:0] warning: continuing with less udp ports: 5820
[1668439651] unbound[1:0] warning: increase ulimit or decrease threads, ports in config to remove this warning

I think its still working fine - but why these Logs and what to do?

Rgds Dario

@MatthewVance
Copy link
Owner

Hi,

I'm not familiar with most of those errors. I wonder if the container isn't getting sufficient resources from the host. You could try adjusting settings on UNRAID or modifying the unbound.sh file to perform different optimization settings and then re-building the Dockerfile. The script tries to intelligent set values based on data it gathers at start up (lines 3-32).

Unfortunately, the first two errors relate udp connect and IPv6 is a known-error that I don't know a resolution for: https://github.com/MatthewVance/unbound-docker#known-issues

@Qianli-Ma
Copy link

Hi - with my fresh UNRAID install i get the following Logs with the Unbound Docker:

[1668439651] libunbound[22:0] error: udp connect failed: Cannot assign requested address for 2001:500:9f::42 port 53 [1668439651] libunbound[22:0] error: udp connect failed: Cannot assign requested address for 2001:dc3::35 port 53 [1668439651] unbound[1:0] warning: setrlimit: Operation not permitted [1668439651] unbound[1:0] warning: cannot increase max open fds from 40960 to 57568 [1668439651] unbound[1:0] warning: continuing with less udp ports: 5820 [1668439651] unbound[1:0] warning: increase ulimit or decrease threads, ports in config to remove this warning

I think its still working fine - but why these Logs and what to do?

Rgds Dario

are you using the one from unraid CA? I've manually changed the repo to mvance/unbound:latest and got rid of the errors

@nodiaque
Copy link

Hi - with my fresh UNRAID install i get the following Logs with the Unbound Docker:
[1668439651] libunbound[22:0] error: udp connect failed: Cannot assign requested address for 2001:500:9f::42 port 53 [1668439651] libunbound[22:0] error: udp connect failed: Cannot assign requested address for 2001:dc3::35 port 53 [1668439651] unbound[1:0] warning: setrlimit: Operation not permitted [1668439651] unbound[1:0] warning: cannot increase max open fds from 40960 to 57568 [1668439651] unbound[1:0] warning: continuing with less udp ports: 5820 [1668439651] unbound[1:0] warning: increase ulimit or decrease threads, ports in config to remove this warning
I think its still working fine - but why these Logs and what to do?
Rgds Dario

are you using the one from unraid CA? I've manually changed the repo to mvance/unbound:latest and got rid of the errors

are you talking about the one that is from kutzilla? Cause I only see one unbound in the CA, it's from kutzilla/unbound:latest which has no update in the last 2 year. I myself have the same error but I'm on kutzilla/unbound:latest. I'll probably switch to this one since it's kind of up to date (Still 2 months late on 1.17.1)

@GlenNicholls
Copy link

GlenNicholls commented Mar 31, 2023

@Qianli-Ma can you provide your run command and any other relevant unRAID config info? I'm seeing similar issues as OP and haven't found a way to get the container to run. For reference, I am using custom unraid.conf for pi-hole. My run command is below:

docker run
  -d
  --name='unbound'
  --net='br0'
  --ip='192.168.1.3'
  -e TZ="America/Denver"
  -e HOST_OS="Unraid"
  -e HOST_HOSTNAME="blah"
  -e HOST_CONTAINERNAME="unbound"
  -l net.unraid.docker.managed=dockerman
  -l net.unraid.docker.icon='https://i.imgur.com/cnsNS1O.png'
  -v '/mnt/user/appdata/unbound':'/opt/unbound/etc/unbound':'rw'
  --user 99:100
  -p 5335:53/tcp
  -p 5335:53/udp 'mvance/unbound:latest'

My errors are:

cp: cannot create special file '/opt/unbound/etc/unbound/dev/random': Operation not permitted
cp: cannot create special file '/opt/unbound/etc/unbound/dev/urandom': Operation not permitted
cp: cannot create special file '/opt/unbound/etc/unbound/dev/null': Operation not permitted
chown: changing ownership of '/opt/unbound/etc/unbound/var': Operation not permitted
[1680223113] unbound[1:0] warning: unbound is already running as pid 1.
[1680223113] unbound[1:0] fatal error: unable to chroot to /opt/unbound/etc/unbound: Operation not permitted

My custom unbound.conf, a-records.conf, and forward-records.conf are in /mnt/user/appdata/unbound. I've changed the docker run command around a LOT to varying degrees of success, but it seems like the root cause is that there's permissions issues. I've tried the root:root user, my personal <me>, nobody:users, privileged, and a couple other combinations along with not specifying the user and opening permissions and running chown on /mnt/users/appdata/unbound and nothing seems to do the trick...

Unbound successfully creates the workspace but without specifying the user, some stuff is created as root and others as my personal user. No matter what I do, unbound throws errors that it can't access something it needs in the working dir.

@realcanadrian
Copy link

Same issue.

text  error  warn  system  array  login  

chown: cannot access '/opt/unbound/etc/unbound/unbound.log': No such file or directory
[1693601225] unbound[1:0] warning: setrlimit: Operation not permitted
[1693601225] unbound[1:0] warning: cannot increase max open fds from 40960 to 189120
[1693601225] unbound[1:0] warning: continuing with less udp ports: 1750
[1693601225] unbound[1:0] warning: increase ulimit or decrease threads, ports in config to remove this warning
[1693601225] unbound[1:0] warning: unbound is already running as pid 1.
[1693601225] unbound[1:0] error: Could not open logfile /dev/null: Permission denied
[1693601225] unbound[1:0] warning: subnetcache: serve-expired is set but not working for data originating from the subnet module cache.
[1693601225] unbound[1:0] warning: subnetcache: prefetch is set but not working for data originating from the subnet module cache.
[1693601225] unbound[1:0] error: unable to open var/root.key for reading: No such file or directory
[1693601225] unbound[1:0] error: error reading auto-trust-anchor-file: var/root.key
[1693601225] unbound[1:0] error: validator: error in trustanchors config
[1693601225] unbound[1:0] error: validator: could not apply configuration settings.
[1693601225] unbound[1:0] error: module init for module validator failed
[1693601225] unbound[1:0] fatal error: failed to setup modules

** Press ANY KEY to close this window ** 

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

6 participants