-
-
Notifications
You must be signed in to change notification settings - Fork 37
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
Unbound segmentation fault on Ubuntu 18.04 LTS #5
Comments
First of all, thanks for the nice layout for the issue 👍 Just to be clear, the container fails at startup right? The image is built every 3 days with the latest updates and malicious hostnames / ips. Maybe try The I tried the latest image without any problem for a few minutes at least. I also fixed a little problem regarding username to drop privileges, so the warning |
Exact same issue on Ubuntu 18.04 with the latest image binding to a non-standard port. It doesn't seem to fail at startup but rather, some time later. Settings |
The container does not always fail on startup. It sometimes fails after it receives a request. For example it restarted automatically after a seg fault two hours ago. Also, I have the malicious filtering turned off. I pulled the latest version and rebuilt, I'll let it run for a while and see what happens. No crashes so far, so fingers crossed. |
It has been crashing still with the same segmentation fault error. |
I just pushed an update to Alpine 3.9 and to Unbound 1.8.3 (from 1.7.3), so that might solve your problem. Give it a try 👍 docker pull qmcgaw/cloudflare-dns-server |
Really appreciate the help. Looking good so far. Will continue monitoring. |
This seems to have fixed it, no crashes in over 24 hours. Thanks for the great work! |
Just a little note; we had segmentation faults since the few last updates because I tried to build unbound from source and somehow it failed every 10 hours approximately. I have reverted back to the Alpine built Unbound and it should work again now. Sorry for the inconvenience! |
Issue
When running on Ubuntu 18.04 LTS, Unbound frequently experiences segmentation faults.
How to replicate
I have disabled systemd-resolved so I could bind the container to port 53 and in /etc/reslolv.conf, the nameserver address is set to 127.0.0.1. The container works with the always restart policy applied but still restarts frequently. I have tried this on Docker for Mac and have not experienced any of these issues. I can provide more information if needed.
Logs
Here is the minimal error log, with a more verbose log below.
Max verbosity log
The text was updated successfully, but these errors were encountered: