Long story short: Containers on one of my QNAPs could access the network fine, while the identical containers on my other QNAP (same model/config) would not.
Figured out that /etc/resolv.conf access control was set to rw-r--r--+ root root - user couldn't access/read that file.
Pulled my hair out trying to figure out what was wrong/different.
Finally realized that the system that wouldn't work had Windows Extended ACLs enabled. Apparently QNAP applied this EVERYWHERE, including /etc
Turned off extended ACLs (I didn't need them anyway), and BOOM! Everything works again.
SOLVED: No network/DNS access from Docker Container (/etc/resolv.conf access error)
-
- First post
- Posts: 1
- Joined: Mon Feb 22, 2016 4:12 am
-
- Know my way around
- Posts: 107
- Joined: Wed Apr 15, 2015 9:08 pm
Re: SOLVED: No network/DNS access from Docker Container (/etc/resolv.conf access error)
I have checked, and i dont seem to have ACL enabled - not ticked.
This is under:
Shared Folders/Advanced Permissions/
When i try to create a container image i get:
Err http://archive.ubuntu.com/ubuntu/ trusty/main libidn11 amd64 1.28-1ubuntu2
Could not resolve 'archive.ubuntu.com'
Err http://archive.ubuntu.com/ubuntu/ trusty/main openssl amd64 1.0.1f-1ubuntu2
Could not resolve 'archive.ubuntu.com'
Err http://archive.ubuntu.com/ubuntu/ trusty/main ca-certificates all 20130906ubuntu2
Could not resolve 'archive.ubuntu.com'
Err http://archive.ubuntu.com/ubuntu/ trusty/main wget amd64 1.15-1ubuntu1
Could not resolve 'archive.ubuntu.com'
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/m ... _amd64.deb Could not resolve 'archive.ubuntu.com'
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/m ... _amd64.deb Could not resolve 'archive.ubuntu.com'
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/m ... u2_all.deb Could not resolve 'archive.ubuntu.com'
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/m ... _amd64.deb Could not resolve 'archive.ubuntu.com'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Also i have:
-rw-r--r-- 1 admin administ 45 Mar 9 22:32 resolv.conf
Should i chmod it to something?
This is under:
Shared Folders/Advanced Permissions/
When i try to create a container image i get:
Err http://archive.ubuntu.com/ubuntu/ trusty/main libidn11 amd64 1.28-1ubuntu2
Could not resolve 'archive.ubuntu.com'
Err http://archive.ubuntu.com/ubuntu/ trusty/main openssl amd64 1.0.1f-1ubuntu2
Could not resolve 'archive.ubuntu.com'
Err http://archive.ubuntu.com/ubuntu/ trusty/main ca-certificates all 20130906ubuntu2
Could not resolve 'archive.ubuntu.com'
Err http://archive.ubuntu.com/ubuntu/ trusty/main wget amd64 1.15-1ubuntu1
Could not resolve 'archive.ubuntu.com'
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/m ... _amd64.deb Could not resolve 'archive.ubuntu.com'
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/m ... _amd64.deb Could not resolve 'archive.ubuntu.com'
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/m ... u2_all.deb Could not resolve 'archive.ubuntu.com'
E: Failed to fetch http://archive.ubuntu.com/ubuntu/pool/m ... _amd64.deb Could not resolve 'archive.ubuntu.com'
E: Unable to fetch some archives, maybe run apt-get update or try with --fix-missing?
Also i have:
-rw-r--r-- 1 admin administ 45 Mar 9 22:32 resolv.conf
Should i chmod it to something?
-
- Starting out
- Posts: 10
- Joined: Tue Nov 24, 2015 4:32 am
Re: SOLVED: No network/DNS access from Docker Container (/etc/resolv.conf access error)
I have also no internet connection from within the container station (lxc-image ubuntu, dockerimage kali-metasploit).
What do I have to do to reenable the internetconnection.
I have not checked the option for extendec ACLs.
A ping to 8.8.8.8 doenst work, a ping to the routers ip doesn work.
Any help?
Edit: Found it by myself....Container Station 1.4.1047 has internetconnection problems version 1.3.85.835 doesnt have it. Time to downgrade
What do I have to do to reenable the internetconnection.
I have not checked the option for extendec ACLs.
A ping to 8.8.8.8 doenst work, a ping to the routers ip doesn work.
Any help?
Edit: Found it by myself....Container Station 1.4.1047 has internetconnection problems version 1.3.85.835 doesnt have it. Time to downgrade
-
- Know my way around
- Posts: 107
- Joined: Wed Apr 15, 2015 9:08 pm
Re: SOLVED: No network/DNS access from Docker Container (/etc/resolv.conf access error)
Can you give me the link to the version 1.3.85.835?
I cant find it.
I cant find it.
-
- Starting out
- Posts: 10
- Joined: Sun May 22, 2011 8:45 pm
- Location: the Netherlands
Re: SOLVED: No network/DNS access from Docker Container (/etc/resolv.conf access error)
See this topicantakar wrote:Can you give me the link to the version 1.3.85.835?
I cant find it.
-
- New here
- Posts: 3
- Joined: Sat Mar 26, 2016 6:46 am
Re: SOLVED: No network/DNS access from Docker Container (/etc/resolv.conf access error)
I found a workaround. I just enabled OpenVPN (and restart NAS) and now my docker containers can access internet with ContainerStation 1.4.1047.
Looks like enabling OpenVPN properly loads NAT kernel modules which are needed by CS, which itself can't load those modules somehow.
I recently bought this TS-453 Pro (upgraded from a Synology DS213j). I like all the flexibility and power but these software issues are frustrating...
Looks like enabling OpenVPN properly loads NAT kernel modules which are needed by CS, which itself can't load those modules somehow.
I recently bought this TS-453 Pro (upgraded from a Synology DS213j). I like all the flexibility and power but these software issues are frustrating...
-
- New here
- Posts: 2
- Joined: Sat Sep 05, 2015 9:34 pm
Re: SOLVED: No network/DNS access from Docker Container (/etc/resolv.conf access error)
This worked for me, but I had to remove and reinstall Container Station after enabling OpenVPN to get it to work correctly.
Simply enabling OpenVPN without reinstalling Container Station gave the same DNS failure results.
Simply enabling OpenVPN without reinstalling Container Station gave the same DNS failure results.
-
- New here
- Posts: 3
- Joined: Sat Mar 26, 2016 6:46 am
Re: SOLVED: No network/DNS access from Docker Container (/etc/resolv.conf access error)
Enable OpenVPN and restart NAS should have worked. But reinstalling Container Station probably is easier...segordon wrote:This worked for me, but I had to remove and reinstall Container Station after enabling OpenVPN to get it to work correctly.
Simply enabling OpenVPN without reinstalling Container Station gave the same DNS failure results.
-
- Starting out
- Posts: 24
- Joined: Fri Sep 18, 2020 12:39 pm
Re: SOLVED: No network/DNS access from Docker Container (/etc/resolv.conf access error)
Hi...
Do the container ip got published under the NAS dns on AD on your box?
Mine keeps showing up and messed up the smb connection.
Do the container ip got published under the NAS dns on AD on your box?
Mine keeps showing up and messed up the smb connection.