After update networking fails with rootless Docker

yurj · November 28, 2025, 9:36am

They found the PR that generates the regression, and there are several workarounds here:

After update (29.0.x) networking fails with rootless Docker (`DOCKERD_ROOTLESS_ROOTLESSKIT_PORT_DRIVER=slirp4netns`)

opened 05:28PM - 25 Nov 25 UTC

status/0-triage kind/bug area/networking area/rootless kind/regression area/networking/portmapping

### Description networking fails with rootless Docker e.g. docker run -it -p 30…00:3080 alpine ash Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint …… failed to bind host port 10.0.2.100:3000/tcp: address already in use It fails regardless which port is picked. (see also https://forums.docker.com/t/after-update-networking-fails-with-rootless-docker/150458) ### Reproduce docker run -it -p 3000:3080 alpine ash ### Expected behavior _No response_ ### docker version ```bash 29.0.4 ``` ### docker info ```bash Client: Docker Engine - Community Version: 29.0.4 Context: rootless Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.30.0 Path: /usr/libexec/docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.40.3 Path: /usr/libexec/docker/cli-plugins/docker-compose ``` ### Additional Info _No response_ - - - **Below is added by @AkihiroSuda** # Workaround: use pasta Tested on Ubuntu 24.04, Docker 29.0.4. Similar to slirp4netns, the src IP information is preserved. ```bash sudo apt install -y passt mkdir -p ~/.config/systemd/user/docker.service.d/ cat <<EOF >~/.config/systemd/user/docker.service.d/override.conf [Service] Environment="DOCKERD_ROOTLESS_ROOTLESSKIT_NET=pasta" Environment="DOCKERD_ROOTLESS_ROOTLESSKIT_PORT_DRIVER=implicit" EOF systemctl --user daemon-reload systemctl --user restart docker ``` # Another Workaround `-p 127.0.0.1:8080:80` and `-p 0.0.0.0:8080:80` seems to work while `-p 8080:80` fails.

yurj · November 28, 2025, 12:40pm

Here the fix: libnet/pm/nat: don't bind IPv6 ports if not supported by port driver by akerouanton · Pull Request #51616 · moby/moby · GitHub so the solution should be soon available.

galaxytrucker · December 3, 2025, 6:18am

It has been fixed in version 29.1.2 which is available now.

Topic		Replies	Views
Fatal iptables/host port errors on 'docker run' after updating to beta18 Docker Desktop	1	2468	July 21, 2016
Docker 29 breaks policy routing General docker , networking , linux	7	131	November 16, 2025
Some containers unreachable after Upgrade to Ubuntu 22.04 General	20	7641	April 19, 2024
Complete failure of Docker General	11	3157	February 18, 2023
IPVLAN L3 driver, forwarding to external DNS resolvers not working General docker	17	2031	April 29, 2024

After update networking fails with rootless Docker

Related topics