Bug#743924: docker.io: Leaves docker0 interface behind after purge

classic Classic list List threaded Threaded
4 messages Options
Reply | Threaded
Open this post in threaded view
|

Bug#743924: docker.io: Leaves docker0 interface behind after purge

Cyril Brulebois-4
Source: docker.io
Version: 0.9.1~dfsg1-1
Severity: important

Hi,

after purging docker.io, I'm still having this configured:
| 4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
|     link/ether 26:d6:1d:34:0d:d3 brd ff:ff:ff:ff:ff:ff
|     inet 172.17.42.1/16 scope global docker0
|        valid_lft forever preferred_lft forever
|     inet6 fe80::24d6:1dff:fe34:dd3/64 scope link
|        valid_lft forever preferred_lft forever

I don't think this should stay upon purge.

Mraw,
KiBi.


--
To UNSUBSCRIBE, email to [hidden email]
with a subject of "unsubscribe". Trouble? Contact [hidden email]

Reply | Threaded
Open this post in threaded view
|

Bug#743924: docker.io: Leaves docker0 interface behind after purge

Paul Tagliamonte-3
On Tue, Apr 08, 2014 at 01:50:44PM +0200, Cyril Brulebois wrote:

> Source: docker.io
> Version: 0.9.1~dfsg1-1
> Severity: important
>
> Hi,
>
> after purging docker.io, I'm still having this configured:
> | 4: docker0: <BROADCAST,MULTICAST,UP,LOWER_UP> mtu 1500 qdisc noqueue state UNKNOWN group default
> |     link/ether 26:d6:1d:34:0d:d3 brd ff:ff:ff:ff:ff:ff
> |     inet 172.17.42.1/16 scope global docker0
> |        valid_lft forever preferred_lft forever
> |     inet6 fe80::24d6:1dff:fe34:dd3/64 scope link
> |        valid_lft forever preferred_lft forever
>
> I don't think this should stay upon purge.
Right you are, thanks, KiBi.

> Mraw,
> KiBi.

Cheers,
  Paul

--
 .''`.  Paul Tagliamonte <[hidden email]>  |   Proud Debian Developer
: :'  : 4096R / 8F04 9AD8 2C92 066C 7352  D28A 7B58 5B30 807C 2A87
`. `'`  http://people.debian.org/~paultag
 `-     http://people.debian.org/~paultag/conduct-statement.txt

signature.asc (836 bytes) Download Attachment
Reply | Threaded
Open this post in threaded view
|

Bug#743924: docker.io: Leaves docker0 interface behind after purge

Tianon Gravi
In reply to this post by Cyril Brulebois-4
On 8 April 2014 at 04:50, Cyril Brulebois <[hidden email]> wrote:
> I don't think this should stay upon purge.

Hmm, I tend to agree, but what if the user has specified "--bridge" on
their daemon to change the bridge interface Docker uses before they
purge?  Or what if they're using "docker0" explicitly configured in
"/etc/network/interfaces" (or elsewhere) for their own use either in
conjunction with or irrespective of Docker?

If we have a good way to determine whether the bridge interface is the
one that Docker automatically created by default, I'm all for purging
it, but otherwise I think this is potentially network-breaking
dangerous territory for us to mess with, isn't it?

♥,
- Tianon
  4096R / B42F 6819 007F 00F8 8E36  4FD4 036A 9C25 BF35 7DD4

Reply | Threaded
Open this post in threaded view
|

Bug#743924: Should be more than minor

Salvo Tomaselli-3
In reply to this post by Cyril Brulebois-4
I just spent 1 hour trying to figure out why my printer was not
working… because it uses an address that is on the same subnet as the
docker0 interface…

This automatic configuration breaks more than it fixes.

I also get DNS resolution issues after installing docker, if I'm using dnsmasq.

--
Salvo Tomaselli

"Io non mi sento obbligato a credere che lo stesso Dio che ci ha dotato di
senso, ragione ed intelletto intendesse che noi ne facessimo a meno."
                -- Galileo Galilei

http://ltworf.github.io/ltworf/