docker and IP config

Hi All: I think this may be the right place to post this… Docker seems to be somehow messing with my IP configuration, for a few apps (for instance yt-dl), anyway. I have no docker containers running or installed. I’m wondering if I can remove it (in YaST) without breaking anything in my system? I think I remember it was installed default, but I’m not sure of that. Thank You!

linux-mubb:/home/patti # ifconfig -a
docker0: flags=4099<UP,BROADCAST,MULTICAST>  mtu 1500
        inet 172.xxx.xxx.xxx  netmask 255.255.0.0  broadcast 172.xxx.255.255
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

eth0: flags=4163<UP,BROADCAST,RUNNING,MULTICAST>  mtu 1500
        inet xxx.xxx.xxx.xxx  netmask 255.255.255.0  broadcast xxx.xxx.1.255
        RX packets 30717814  bytes 43559461295 (40.5 GiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 16409780  bytes 1411964753 (1.3 GiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0
        device interrupt 20  memory 0xcca00000-cca20000  

lo: flags=73<UP,LOOPBACK,RUNNING>  mtu 65536
        inet 127.0.0.1  netmask 255.0.0.0
        inet6 ::1  prefixlen 128  scopeid 0x10<host>
        loop  txqueuelen 1000  (Local Loopback)
        RX packets 89250  bytes 105100820 (100.2 MiB)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 89250  bytes 105100820 (100.2 MiB)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

wlan0: flags=4098<BROADCAST,MULTICAST>  mtu 1500
        RX packets 0  bytes 0 (0.0 B)
        RX errors 0  dropped 0  overruns 0  frame 0
        TX packets 0  bytes 0 (0.0 B)
        TX errors 0  dropped 0 overruns 0  carrier 0  collisions 0

cat /etc/hosts

#                                                                                                                                               
# hosts         This file describes a number of hostname-to-address                                                                             
#               mappings for the TCP/IP subsystem.  It is mostly                                                                                
#               used at boot time, when no name servers are running.                                                                            
#               On small systems, this file can be used instead of a                                                                            
#               "named" name server.                                                                                                            
# Syntax:                                                                                                                                       
#                                                                                                                                               
# IP-Address  Full-Qualified-Hostname  Short-Hostname                                                                                           
#                                                                                                                                               
                                                                                                                                                
127.0.0.1             linux-mubb.suse   localhost                                                                                               
                                                                                                                                               

# special IPv6 addresses
::1             localhost ipv6-localhost ipv6-loopback

fe00::0         ipv6-localnet

ff00::0         ipv6-mcastprefix
ff02::1         ipv6-allnodes
ff02::2         ipv6-allrouters
ff02::3         ipv6-allhosts



What do you mean by “messing with… configuration?”
Is something not working properly?
Docker networking however you are configured should be isolated from, and not affect the networking of anything else running on your box.

BTW -
You should get in the habit of not using ifconfig, besides not being part of a default install, the kernel “ip” commands almost all display more useful info than their legacy predecessors.

TSU

I have Leap 15.1 and have no packages with the string “docker” in the name installed. So I assume you can live without them and that they are not installed by default.

Without more analysis, one can’t be sure but a pretty good guess is that it’s a bridge device (like br0 but configured differently).

TSU

I do not understand this, sorry.

I thought the main question was: can I remove the docker package(s) or is it a normal part of any installation (e.g. because it is installed by default). And that what I try to answer by telling that I have no docker packages at all, I did not remove them, thus they are not part of the default installation and my system is running happily.
I can not connect your answer/comment to my post with what I am trying to tell.

The @OP question was about her network configuration, and I assume the reported docker interface, not docker itself… not about docker packages.
It’s anyone’s guess how the docker interface was created.

Bottom line though, is that since it’s likely a bridge interface, it would be associated with, and not a “real” interface so can be deleted safely.
Or, it can be left alone… As I described it should not affect how networking works for anything else on the machine.

TSU

I do see the connection between your answer and the original post, but you quoted me and not (a snippet of) the original post and I do not see a connection there.

@PattiMichelle: simply uninstall docker. As soon as the docker service starts, the virtual device is created, hence the docker0

+1 from me, which is what Henk was also hinting at. :wink:

Looking more closely at docker0,
It is indeed a bridge device and
As I also suspected, simply uninstalling docker will not remove it.

As I described above, because this is a bridge device it’s not associated directly with a specific physical device, so it can be removed using YaST, brctl or ip utilities.
On the other hand, like any other bridge device it does not affect anything by simply existing so you can safely leave it on your system.

TSU

Thanks everyone! I did uninstall docker, but it didn’t fix the problem. For some reason, there seems to be an IP issue with only one app:

~/Videos> youtube-dl https://www.youtube.com/watch?v=OKUUomFA5hQ
https://www.youtube.com/watch?v= OKUUomFA5hQ: Downloading webpage
ERROR: Unable to download webpage: <urlopen error no host given> (caused by URLError('no host given',))
~/Videos>

I’m not sure what that output means.

That downloads the mp4 fine here. On TW, that is.

[QUOTE=PattiMichelle;2912188]Thanks everyone! I did uninstall docker, but it didn’t fix the problem. For some reason, there seems to be an IP issue with only one app:

~/Videos> youtube-dl https://www.youtube.com/watch?v=OKUUomFA5hQ
https://www.youtube.com/watch?v=

A quick Google search turns up hits, they all say to update your app to the latest version (apparently it's a bug which shows up from time to time)
The following is supposed to fix your problem.

youtube-dl -U



Next, better to open a new thread for a new problem.

TSU

Yes, I’ve been doing that for a while - no results. At one point I uncovered an odd IP address (something like 174.xxx.xxx.xxx), which I can’t replicate now, which I thought was coming from docker. Thanks for helping me verify it wasn’t docker. :slight_smile:

But it is a “something is wrong with my system” issue, so I think it belongs here… to demonstrate, I removed youtubedl from YaST and…

~> sudo curl -L https://yt-dl.org/downloads/latest/youtube-dl -o /usr/local/bin/youtube-dl
[sudo] password for root: 
  % Total    % Received % Xferd  Average Speed   Time    Time     Time  Current
                                 Dload  Upload   Total   Spent    Left  Speed
  0     3    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
  0     3    0     0    0     0      0      0 --:--:--  0:00:01 --:--:--     0
100   599    0   599    0     0    304      0 --:--:--  0:00:01 --:--:--   304
100 1724k  100 1724k    0     0   623k      0  0:00:02  0:00:02 --:--:-- 3224k
~> sudo chmod a+rx /usr/local/bin/youtube-dl
~> youtube-dl -v https://www.youtube.com/watch?v=OKUUomFA5hQ
[debug] System config: ]
[debug] User config: ]
[debug] Custom config: ]
[debug] Command-line args: 
[debug] Encodings: locale UTF-8, fs UTF-8, out UTF-8, pref UTF-8
[debug] youtube-dl version 2018.12.17
[debug] Python version 2.7.13 (CPython) - Linux-4.12.14-lp150.12.70-default-x86_64-with-glibc2.2.5
[debug] exe versions: ffmpeg 3.4.4, ffprobe 3.4.4
[debug] Proxy map: {'http': 'http://', u'https': 'http://'}
https://www.youtube.com/watch?v= OKUUomFA5hQ: Downloading webpage
ERROR: Unable to download webpage: <urlopen error no host given> (caused by URLError('no host given',))
  File "/home/patti/bin/youtube-dl/youtube_dl/extractor/common.py", line 605, in _request_webpage
    return self._downloader.urlopen(url_or_request)
  File "/home/patti/bin/youtube-dl/youtube_dl/YoutubeDL.py", line 2212, in urlopen
    return self._opener.open(req, timeout=self._socket_timeout)
  File "/home/patti/vapor-2.6.0/lib/python2.7/urllib2.py", line 429, in open
    response = self._open(req, data)
  File "/home/patti/vapor-2.6.0/lib/python2.7/urllib2.py", line 447, in _open
    '_open', req)
  File "/home/patti/vapor-2.6.0/lib/python2.7/urllib2.py", line 407, in _call_chain
    result = func(*args)
  File "/home/patti/bin/youtube-dl/youtube_dl/utils.py", line 1140, in https_open
    req, **kwargs)                                                                                                                                  
  File "/home/patti/vapor-2.6.0/lib/python2.7/urllib2.py", line 1164, in do_open                                                                    
    raise URLError('no host given')
~>

It’s still a coding error, and apparently it’s re-appeared even in its latest version.

This is the youtube-dl project
https://github.com/ytdl-org/youtube-dl

Looks like the latest version in the project is 2019.8.13, and that is also the version available in openSUSE and what you likely installed directly from yt-dl.org
First,
You might install youtube-dl in another machine (even a virtual machine) and try downloading again just to verify the unlikelihood it’s something unique to your installation,
Then if you still see the problem, I’d recommend you create a issue at the github project (You’ll get fastest response that way)

EDIT -
Try running as a normal User, and don’t sudo.
Of course, you’ll have to d/l to a subdirectory of /home.
Am wondering if you might be encountering an AppArmor issue which might restrict web applications from running with root permissions.

TSU

…so that means it’s a system issue? (not a youtbe-dl issue) Docker did generate the 172.xxx.xxx.xxx IP, which ifconfig -a verifies is gone, and only my current machine is listed in my hosts file. Very odd! I use the standard opensuse yt-dl on all my systems. I wonder if I should try an online update to 15.1?

It’s only this one LEAP machine which is having issues (my main machine). My other two laptops don’t have issues with yt-dl. So I’m pretty sure there’s an obscure problem with my system setup on this particular machine. However, I’m not linux-savvy enough to diagnose (beyond looking at /etc/hosts for irregularities). I have occasionally used openvpn on this system, and I’m wondering if openvpn interacted badly with the YaST System Configurator files, or something, so that yt-dl gets confused. Now that I recall, it was about the time I started using openvpn that the yt-dl issue arose.

I guess I’ll let it go for now. Everyone, thanks for the replies.

It doesn’t appear to be a network configuration issue, it’s almost certainly an application issue.
You might try uninstalling the application and then re-installing.
Since I highly doubt that the problem is in a configuration file, you shouldn’t need to consider purging the remnants of the old install before installing new.
If you haven’t been uninstalling before installing new from yt-dl, you might not have removed the problem so the new install might have been corrupted by whatever was in the previous install.

TSU