docker.io docker-proxy only binds to ipv4

Bug #1929931 reported by Paul Tötterman
20
This bug affects 4 people
Affects Status Importance Assigned to Milestone
docker.io (Ubuntu)
Confirmed
Undecided
Unassigned

Bug Description

Hi,

When running e.g.

    docker run --rm -it -p 80:80 traefik/whoami

this results in docker-proxy only listening on 0.0.0.0:80. And because of this

    curl -4 hostname

works, but

    curl -6 hostname

doesn't. It is meant to work, and this seems to be fixed in later docker versions:

https://github.com/moby/libnetwork/issues/2607

https://github.com/moby/moby/issues/42059

So, please get those fixes (20.10.6?) into ubuntu.

Thanks,
Paul

Revision history for this message
Launchpad Janitor (janitor) wrote :

Status changed to 'Confirmed' because the bug affects multiple users.

Changed in docker.io (Ubuntu):
status: New → Confirmed
Revision history for this message
Reinhard Koehn (rekoehn) wrote :

Some additional information from docker release notes:

docker.io 20.10.2 introduced a regression that disabled binding to ipv6 addresses: https://github.com/moby/moby/issues/41858

This regression was fixed in docker 20.10.6, see https://docs.docker.com/engine/release-notes/#20106 , fix is part of merged https://github.com/moby/moby/pull/42205

Please update docker.io in focal-updates to 20.10.6 to fix these regressions that impact many users using ipv6 with docker.io.

To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.