-
Notifications
You must be signed in to change notification settings - Fork 143
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
Comments
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 |
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) |
@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
My errors are:
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 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. |
Same issue.
|
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
The text was updated successfully, but these errors were encountered: