Page 1 of 2 12 LastLast
Results 1 to 10 of 18

Thread: docker and IP config

  1. #1
    Join Date
    Jun 2008
    Location
    Prescott, AZ
    Posts
    1,175

    Default 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!

    Code:
    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
    Code:
    #                                                                                                                                               
    # 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

  2. #2
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,105
    Blog Entries
    2

    Default Re: docker and IP config

    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
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  3. #3
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,973

    Default Re: docker and IP config

    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.
    Henk van Velden

  4. #4
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,105
    Blog Entries
    2

    Default Re: docker and IP config

    Quote Originally Posted by hcvv View Post
    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
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  5. #5
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,973

    Default Re: docker and IP config

    Quote Originally Posted by tsu2 View Post
    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.
    Henk van Velden

  6. #6
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,105
    Blog Entries
    2

    Default Re: docker and IP config

    Quote Originally Posted by hcvv View Post
    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
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

  7. #7
    Join Date
    Jun 2008
    Location
    Netherlands
    Posts
    24,973

    Default Re: docker and IP config

    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.
    Henk van Velden

  8. #8
    Join Date
    Jun 2008
    Location
    Groningen, Netherlands
    Posts
    19,763
    Blog Entries
    14

    Default Re: docker and IP config

    @PattiMichelle: simply uninstall docker. As soon as the docker service starts, the virtual device is created, hence the docker0
    ° Appreciate my reply? Click the star and let me know why.

    ° Perfection is not gonna happen. No way.

    https://en.opensuse.org/openSUSE:Board#Members
    http://en.opensuse.org/User:Knurpht
    http://nl.opensuse.org/Gebruiker:Knurpht

  9. #9
    Join Date
    Jun 2008
    Location
    Auckland, NZ
    Posts
    20,260
    Blog Entries
    1

    Default Re: docker and IP config

    Quote Originally Posted by Knurpht View Post
    @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.
    openSUSE Leap 15.0; KDE Plasma 5

  10. #10
    Join Date
    Jun 2008
    Location
    San Diego, Ca, USA
    Posts
    11,105
    Blog Entries
    2

    Default Re: docker and IP config

    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
    Beginner Wiki Quickstart - https://en.opensuse.org/User:Tsu2/Quickstart_Wiki
    Solved a problem recently? Create a wiki page for future personal reference!
    Learn something new?
    Attended a computing event?
    Post and Share!

Page 1 of 2 12 LastLast

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •