Package: docker.io
Version: 20.10.5+dfsg1-1+b1
Severity: important
Tags: ipv6
Dear Maintainer,
* What led up to the situation?
I'm trying to expose some web app to the ipv6 Internet !
* What exactly did you do (or not do) that was effective (or
ineffective)?
I enabled ipv6 support in /etc/docker/daemon.json as explained in docker doc.
* What was the outcome of this action?
Exposed ports are only on ipv4 even if ipv6 is enabled in docker configuration.
* What outcome did you expect instead?
The binding shall be done on both ipv4 and ipv6 networks.
The issue is confirmed upstream : https://github.com/moby/moby/issues/42059
It is due to https://github.com/moby/libnetwork/issues/2607
It seems to be fixed already, and packaged in version 20.10.6 that has been
just released.
-- System Information:
Debian Release: bullseye/sid
APT prefers testing
APT policy: (850, 'testing'), (500, 'unstable')
Architecture: amd64 (x86_64)
Foreign Architectures: i386
Kernel: Linux 5.10.0-6-amd64 (SMP w/8 CPU threads)
Kernel taint flags: TAINT_OOT_MODULE, TAINT_UNSIGNED_MODULE
Locale: LANG=fr_FR.UTF-8, LC_CTYPE=fr_FR.UTF-8 (charmap=UTF-8), LANGUAGE not
set
Shell: /bin/sh linked to /usr/bin/dash
Init: systemd (via /run/systemd/system)
LSM: AppArmor: enabled
Versions of packages docker.io depends on:
ii adduser 3.118
ii containerd 1.4.4~ds1-2
ii init-system-helpers 1.60
ii iptables 1.8.7-1
ii libc6 2.31-11
ii libdevmapper1.02.1 2:1.02.175-2.1
ii libsystemd0 247.3-3
ii lsb-base 11.1.0
ii runc 1.0.0~rc93+ds1-2+b2
ii tini 0.19.0-1
Versions of packages docker.io recommends:
ii apparmor 2.13.6-10
ii ca-certificates 20210119
ii cgroupfs-mount 1.4
ii git 1:2.30.2-1
ii needrestart 3.5-2
ii xz-utils 5.2.5-2
Versions of packages docker.io suggests:
ii aufs-tools 1:4.14+20190211-1
pn btrfs-progs <none>
pn debootstrap <none>
pn docker-doc <none>
ii e2fsprogs 1.46.2-1
pn rinse <none>
pn rootlesskit <none>
pn xfsprogs <none>
pn zfs-fuse | zfsutils-linux <none>
