-
Notifications
You must be signed in to change notification settings - Fork 24
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
DNS resolution not working even after container is destroyed/recreated #16
Comments
31 Oct 2020: sadly, due to legal obligations arising from a recent change in my 'real world' job, I must announce I am standing down as maintainer of this project with immediate effect. For the meantime, I will leave the repo up (for historical interest, and since the Debian package is still in the official Raspbian repos); however, there will be no further updates to the underlying OS images etc., nor will I be accepting / actioning further pull requests or bug reports from this point. Email requests for support will also have to be politely declined, so, please treat this as an effective EOL notice. |
I have installed successfully the container on a Pi4 with the latest Raspbian version, everything was working fine but yesterday the DNS resolution inside the container stopped working, I was unable to fix the issue and I have recreated the container because I need it for docker and DNS resolution is essential. Container recreation works fine until I reboot, after reboot the container works, docker works but DNS resoltion doesn't works anymore. If can be useful I am using OMV on the same installation, but on a same setup on another microSD they are living together fine, and the procedure was the same...
The text was updated successfully, but these errors were encountered: