Jump to content
ruthlessone

Running into what i think is a docker networking issue

27 posts in this topic Last Reply

Recommended Posts

Setting up a SABNZBD Docker after dropping the Phaze plugins. The docker installs and I get to the Wizard and enter in my usegroup providers site address and I get:

 [Errno 111] (110, '[Errno 101] Network is unreachable')

Tried multiple (i know are good) addresses and i get the same. 

 

Tried deleting the ini files and have it recreate.. Nope same. Tired the same on NZBGET docker... Same issue... so it makes me think Docker Networking??

 

 

Share this post


Link to post

Post a screenshot of the docker settings of this container

Share this post


Link to post
Posted (edited)

bonienl here you go, thanks for taking a look, I have spun my wheels on this for a while!

Screenshot 2019-04-12 at 9.06.22 AM.png

 

Details about my network: ATT Uverse Gigapower Fiber -> Hardwired into DMZd Google WIFI where all it goes into a switch to the rest of the house, and the wired devices (including unraid) and wifi. All machines including UNraid (plex docker) are functioning as expected. 

Edited by ruthlessone
add network details

Share this post


Link to post

The container is set to use the host network, which means it is directly accessing the interface, similar as Unraid itself. When Unraid has network/internet access so should have the container.

 

Do you have any other containers running or configured with the same ports 8080 or 8090?

 

Share this post


Link to post

I do not. Only 5 dockers and none on that port. AND the UPNP automatically added those 2 ports to the firewall in google wifi app.  Even if I skip and get into the settings of SAB, whenever an attempt is made to validate the link for a Usenet, I get that error immediately, behaving like it doesn't have DNS or Internet. 

 

Capture.JPG

Share this post


Link to post

Post a screenshot of your network settings

Share this post


Link to post

I don't see anything wrong in your network settings.

A minor thing, you have enabled IPv6 but your router is not giving out IPv6 addresses, though this should not be an issue.

 

You can use the 'console' function of the failing container and do the following. What is the result?

ping 8.8.8.8

 

Share this post


Link to post

I'm using the 'bridge' settings in Unraid. Working for 8 dockets or something

Verstuurd vanaf mijn SNE-LX1 met Tapatalk

Share this post


Link to post
Posted (edited)

response as expected (ping reply) from that container... hmm. when I try to ping https://api.NZBPROVIDER.info/ or api.NZBPROVIDER.info/ it returns nothing. I paste that same thing in lookup tool on the web and it works fine. 

 

When i resolve the IP of the above address and then ping that IP, it works from the container. So DNS?

 

What is next step in troubleshooting?

Edited by ruthlessone
more info

Share this post


Link to post
22 minutes ago, Impulse1337 said:

I'm using the 'bridge' settings in Unraid. Working for 8 dockets or something

Verstuurd vanaf mijn SNE-LX1 met Tapatalk
 

I've tried Bridge as well same behavior... 

Share this post


Link to post
I've tried Bridge as well same behavior... 
This is my setup. Not sure why it isn't working thod2384126fc38d7c1851c8375dd7f0326.jpg

Verstuurd vanaf mijn SNE-LX1 met Tapatalk

Share this post


Link to post
1 hour ago, ruthlessone said:

What is next step in troubleshooting?

Do you have the "--dns" parameter set for this container (see extra parameters field in advanced view) ?

Share this post


Link to post

Switch to advanced view

image.png.f23566a517e7a8df1b93043023cee069.png

 

I expect no DNS setting here (extra parameters)

Share this post


Link to post

 

16 minutes ago, bonienl said:

Switch to advanced view

image.png.f23566a517e7a8df1b93043023cee069.png

 

I expect no DNS setting here (extra parameters)

Here it is in advanced view, Umask? Doesn't seem to be any DNS entries. I can add, just need to know what to fill in. 

 

Screenshot 2019-04-14 at 12.13.44 PM.png

Share this post


Link to post

Two things to check first

  1. Open a terminal session and type
    cat /etc/resolv.conf

     

  2. Open a console session of the container and type
     

    cat /etc/resolv.conf

     

Post the results.

Share this post


Link to post

@Mothership:~# cat /etc/resolv.conf
# Generated DNSv4 entries:
nameserver 8.8.8.8
nameserver 192.168.86.1

 

then in container..

 

sh-5.0# cat /etc/resolve.conf
cat: /etc/resolve.conf: No such file or directory
sh-5.0#

 

 

Share this post


Link to post

Your "mothership" is alright :)

 

Container syntax is

cat /etc/resolv.conf

 

Share this post


Link to post

Duh :) 

 

sh-5.0# cat /etc/resolv.conf
# Generated DNSv4 entries:
nameserver 8.8.8.8
nameserver 192.168.86.1

Share this post


Link to post

Inside a container, you should see something like this

root@b142de55abf9:/# cat /etc/resolv.conf
nameserver 127.0.0.11
options ndots:0

 

Share this post


Link to post

sh-5.0# cat /etc/resolv.conf
# Generated DNSv4 entries:
nameserver 8.8.8.8
nameserver 192.168.86.1

 

Ok, so mine doesn't, what does that mean?

Share this post


Link to post
41 minutes ago, ruthlessone said:

Ok, so mine doesn't, what does that mean?

Sorry, I was mixing up things.

In case of a host network your DNS settings are okay.

I am puzzled why it isn't working.... maybe change your DNS to a single entry and see if that works?

Share this post


Link to post

Not sure how to change that? Command line? Variable? suspect you think I a bit more advanced than I really am. 

Share this post


Link to post

Join the conversation

You can post now and register later. If you have an account, sign in now to post with your account.
Note: Your post will require moderator approval before it will be visible.

Guest
Reply to this topic...

×   Pasted as rich text.   Restore formatting

  Only 75 emoji are allowed.

×   Your link has been automatically embedded.   Display as a link instead

×   Your previous content has been restored.   Clear editor

×   You cannot paste images directly. Upload or insert images from URL.