DNS problems [solved by disabling apparmor] #497
Comments
|
I think, one of the problem is apparmor .... |
|
I confirm that disabling apparmor on ubuntu host there are no problems |
|
can you post the dmesg? So I can fix the profile. |
|
Is this related to #448? I can't run HassIO on RPi3 using the official image because of those DNS issues... |
|
Here the log |
|
@Diaoul and check if there is a process named socat |
|
There is no Here is the result on An internet DNS query: And a local DNS query just for fun: Here is the |
|
I fix the profile. If you rerun the installer, they should be done (for generic installation) |
|
Perfect! Now it work! and the syslog Thank you very much! |
|
Will this change be made available for hassio images on RPi or is it just
for manual installs?
|
|
Only manual (generic) installation. We add support to supervisor to auto update the profile later in 1-2 weeks. |
|
@straccio look like your system use the default docker for supervisor. Do you have use the installer? |
|
yes, with this command |
|
create a file called {
"dns": ["192.168.25.25", "8.8.8.8", "8.8.4.4"]
}P.s. the above case is my personal setting and contains a DNS server in my local network (the Pi-Hole add-on). Be sure to customize this matching your network. Afterwards run:
|
|
Can you tell me how you disabled |
|
This is no longer an issue, passing in manual DNS servers using a Docker has fixed this in their project now and is awaiting a release of the next Docker version. |
|
Did not work for me, I installed fresh docker version yesterday, and hass.io is updated to 0.86.4 and I still can't get DNS to work. I have to go into container and edit resolv.conf manually each time. I tried eidting daemon.json and restarting docker, restarting the whole server, still no luck. Am I missing any steps? Do I have to reinstall hass container for it to update something? |
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Good morning and good job.
I have installed hassio with docker on Ubuntu.
All work ok except the dns resolution of "homeassistant" container.
I tried to reinstall all the containers but I did not solve them
After some days digging in internet and looking for a solution in the sources... i have found the problem.
The hassio_supervisor container does not start socat for forward dns (but why you need a dns forwarder to docker dns instead use docker dns directly when launching homeassistant container?)
Running socat command manually or change homeassistant configuration in order to use directly 127.0.0.11 instead hassio_supervisior for dns resolution solve the problem
here some logs and info
The text was updated successfully, but these errors were encountered: