Why my docker so stupid docker proxy infinity alive

soulicephoenix · July 16, 2025, 11:07am

I have 2 project:
Old Project (not use): light.local (8001 for http)
New Project: lightla.local (8001 for http, 8443 for https)
all same local host: 127.0.0.1

I delete all, no have any container, no have any volumn, but light.local still worked
I try everything but still worked.

docker compose down --volumes --remove-orphans
docker system prune -af --volumes
wsl --shutdown, wsl

Anything anyway, but docker proxy always alive

$ sudo ss -tulpn | grep :8001
tcp LISTEN 0 4096 0.0.0.0:8001 0.0.0.0:* users:((“docker-proxy”,pid=20512,fd=4))
tcp LISTEN 0 4096 [::]:8001 [::]:* users:((“docker-proxy”,pid=20535,fd=4))

I can kill process, but when docker compose up from new project, just still alive
I dont’ know what is happen and how to delete linked

rimelek · July 16, 2025, 11:24am

We usually need the following information to understand the issue:

What platform are you using? Windows, Linux or macOS? Which version of the operating systems? In case of Linux, which distribution?
How did you install Docker? Sharing the platform almost answers it, but only almost. Direct links to the followed guide can be useful.
On debian based Linux, the following commands can give us some idea and recognize incorrectly installed Docker:
```
docker info
docker version
```
Review the output before sharing and remove confidential data if any appears (public IP for example)
```
dpkg -l 'docker*' | grep '^ii'
snap list docker
```
When you share the outputs, always format your posts according to the following guide: How to format your forum posts

soulicephoenix · July 16, 2025, 12:07pm

Hi, thanks you support, I use docker on wsl2 windows

Windows WSL2
Ubuntu 22.04.5 LTS

docker version

version: 27.5.1

Client:
 Version:           27.5.1
 API version:       1.47
 Go version:        go1.22.2
 Git commit:        27.5.1-0ubuntu3~22.04.2
 Built:             Mon Jun  2 12:18:38 2025
 OS/Arch:           linux/amd64
 Context:           default

Server:
 Engine:
  Version:          27.5.1
  API version:      1.47 (minimum version 1.24)
  Go version:       go1.22.2
  Git commit:       27.5.1-0ubuntu3~22.04.2
  Built:            Mon Jun  2 12:18:38 2025
  OS/Arch:          linux/amd64
  Experimental:     false
 containerd:
  Version:          1.7.24
  GitCommit:
 runc:
  Version:          1.1.12-0ubuntu2~22.04.1
  GitCommit:
 docker-init:
  Version:          0.19.0
  GitCommit:

docker info # I just delete Docker Desktop after issue docker-proxy

Client:
 Version:    27.5.1
 Context:    default
 Debug Mode: false
 Plugins:
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-ai" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-ai: input/output error
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-buildx" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-buildx: input/output error
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-cloud" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-cloud: input/output error
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-compose" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-compose: input/output error
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-debug" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-debug: input/output error
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-desktop" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-desktop: input/output error
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-dev" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-dev: input/output error
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-extension" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-extension: input/output error
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-init" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-init: input/output error
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-mcp" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-mcp: input/output error
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-sbom" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-sbom: input/output error
WARNING: Plugin "/usr/local/lib/docker/cli-plugins/docker-scout" is not valid: failed to fetch metadata: fork/exec /usr/local/lib/docker/cli-plugins/docker-scout: input/output error

Server:
 Containers: 6
  Running: 5
  Paused: 0
  Stopped: 1
 Images: 6
 Server Version: 27.5.1
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Using metacopy: false
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: json-file
 Cgroup Driver: systemd
 Cgroup Version: 2
 Plugins:
  Volume: local
  Network: bridge host ipvlan macvlan null overlay
  Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog
 Swarm: inactive
 Runtimes: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version:
 runc version:
 init version:
 Security Options:
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.6.87.2-microsoft-standard-WSL2
 Operating System: Ubuntu 22.04.5 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 16
 Total Memory: 7.602GiB
 Name: DESKTOP-OPSNBJQ
 ID: f269dd7e-9dce-42fb-a081-138eb56e1ec8
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No swap limit support

dpkg -l 'docker*' | grep '^ii'

ii  docker-compose-v2 2.27.1+ds1-0ubuntu1~22.04.1 amd64        tool for running multi-container applications on Docker
ii  docker.io         27.5.1-0ubuntu3~22.04.2     amd64        Linux container runtime

snap list docker
=> error: no matching snaps installed

rimelek · July 16, 2025, 8:08pm

Thank you for the well-formatted details!

It seems that you are not using the Docker CE package supported by Docker Inc. So if there is a bug in that docker.io package, that could be fixed by the maintainers of Ubuntu who are the maintainers of the docker.io package as well (or fixed in the moby project. More about that later).

Here is the official guide for the installation of Docker CE on Ubuntu

I can’t tell you if the problem is that you are using the docker.io package or something totally unrelated, but if there was a bug in Docker at some point it was probably fixed as I could not reproduce it with Docker CE 28.1.1 in a test virtual Ubuntu 24.04 machine.

So if a knewer version of docker.io is available, you can try to update to that version. If there is no new version, I recommend installing Docker CE or contacting the Ubuntu maintainers. You can also continue discussing the issue here, since we don’t know if it is a bug in Docker CE as well (until we test the issue with Docker CE 27.5.1).

I think v27 is still supported, so if we can reproduce the issue in that, you could report it in the moby repository

This is the base of the docker.io package as well.

And I found that this issue happened with Docker 20.10 once, so I can imagine it returning

github.com/docker/cli

docker-proxy process doesn't exit after container is stop/removed, if host part of "docker run -p" is IPv6.

opened 07:18AM - 27 Dec 20 UTC

closed 12:13AM - 07 Jan 21 UTC

dawnfantasy

area/networking status/more-info-needed version/20.10

**Description** For IPv4, if you specify "-p 192.168.0.1:80:80" in docker run…, it starts a docker-proxy for you and kills it when the container stops. For IPv6, this action does not happen. the docker-proxy keeps running and listening to the port. **Steps to reproduce the issue:** 1. add an IPv6 to eth0 or another interface. `$ sudo ip addr add fc00:abcd::1/64 dev eth0 ` 2. start container, verify port listening. `$ docker run -itd --rm -p [fc00:abcd::1]:1000:80 --name mynginx nginx ` 3f80f9128f801b1e6428c79f4cc04888cc6f3996499347cb6d036b3a548427ea `$ sudo ss -plnt | grep 1000 ` LISTEN 0 128 [fc00: abcd::1]:1000 [::]:* users:(("docker-proxy",pid=2735,fd=4)) 3. stop nginx, verify port listening. `$ docker stop mynginx ` mynginx `$ sudo ss -plnt | grep 1000 ` LISTEN 0 128 [fc00: abcd::1]:1000 [::]:* users:(("docker-proxy",pid=2735,fd=4)) 4. if I manually kill the docker-proxy process - the process becomes [defunct] - the port is not freed - it doesn't show in netstat/ss - won't be able to listen to that IP/port combination again (docker fails to start) **Describe the results you received:** The port is in LISTEN state and the docker-proxy is still running. **Describe the results you expected:** docker-proxy stops and frees the port. **Additional information you deem important (e.g. issue happens only occasionally):** IPv6 address in -p parameter. **Output of `docker version`:** ``` Client: Docker Engine - Community Version: 20.10.1 API version: 1.41 Go version: go1.13.15 Git commit: 831ebea Built: Tue Dec 15 04:34:58 2020 OS/Arch: linux/amd64 Context: default Experimental: true Server: Docker Engine - Community Engine: Version: 20.10.1 API version: 1.41 (minimum version 1.12) Go version: go1.13.15 Git commit: f001486 Built: Tue Dec 15 04:32:52 2020 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.4.3 GitCommit: 269548fa27e0089a8b8278fc4fc781d7f65a939b runc: Version: 1.0.0-rc92 GitCommit: ff819c7e9184c13b7c2607fe6c30ae19403a7aff docker-init: Version: 0.19.0 GitCommit: de40ad0 ``` **Output of `docker info`:** ``` $ docker info Client: Context: default Debug Mode: false Plugins: app: Docker App (Docker Inc., v0.9.1-beta3) buildx: Build with BuildKit (Docker Inc., v0.5.0-docker) Server: Containers: 3 Running: 0 Paused: 0 Stopped: 3 Images: 1 Server Version: 20.10.1 Storage Driver: vfs Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 1 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc io.containerd.runc.v2 io.containerd.runtime.v1.linux Default Runtime: runc Init Binary: docker-init containerd version: 269548fa27e0089a8b8278fc4fc781d7f65a939b runc version: ff819c7e9184c13b7c2607fe6c30ae19403a7aff init version: de40ad0 Security Options: seccomp Profile: default Kernel Version: 4.20.8-1.el7.elrepo.x86_64 Operating System: Ubuntu 20.04.1 LTS OSType: linux Architecture: x86_64 CPUs: 1 Total Memory: 976.6MiB Name: v2.xxxxy.org ID: PK3O:5R5V:N7JR:OMUR:Y4YO:G75Y:JQJT:MHO2:AEWM:Z2PD:DPUR:VNPP Docker Root Dir: /var/lib/docker Debug Mode: false HTTP Proxy: http://v1.xx.org:33080 HTTPS Proxy: https://v1.xx.org:33080 Registry: https://index.docker.io/v1/ Labels: Experimental: false Insecure Registries: 127.0.0.0/8 Live Restore Enabled: false WARNING: bridge-nf-call-iptables is disabled WARNING: bridge-nf-call-ip6tables is disabled ``` **Additional environment details (AWS, VirtualBox, physical, etc.):**

If you have a way to test Docker CE 27.5.1 and reproduce the same issue in a test environment that could speed up the debugging

emirhanmetin · July 17, 2025, 7:43am

Hi there, I had the same issue. I was trying to run Grafana on port 3000 on my server, but Docker’s proxy was also binding port 3000, blocking traffic. I couldn’t start Grafana until I fixed it. Here’s how I solved it:

Remove docker.io completely:

sudo apt remove docker.io docker-compose-v2 -y
sudo apt autoremove -y
sudo rm -rf /var/lib/docker /etc/docker ~/.docker

Install official Docker CE

sudo apt-get update
sudo apt-get install -y ca-certificates curl gnupg

sudo install -m 0755 -d /etc/apt/keyrings
curl -fsSL https://download.docker.com/linux/ubuntu/gpg | sudo gpg --dearmor -o /etc/apt/keyrings/docker.gpg

echo "deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.gpg] https://download.docker.com/linux/ubuntu $(lsb_release -cs) stable" | sudo tee /etc/apt/sources.list.d/docker.list > /dev/null

sudo apt-get update
sudo apt-get install -y docker-ce docker-ce-cli containerd.io docker-buildx-plugin docker-compose-plugin

After installation, verify Docker version:

docker version

To avoid port conflicts, in your docker-compose.yml bind ports to localhost explicitly:

ports:
  - "127.0.0.1:8001:8001"

When you stuck at ports, fully restart WSL2 to reset networking:

wsl --shutdown

Then start your containers again.

rimelek · July 17, 2025, 9:22am

So it is indeed a bug in docker.io if that helped. (or in the version of moby that the docker io package was based on)

system · August 16, 2025, 9:22am

This topic was automatically closed 30 days after the last reply. New replies are no longer allowed.

Topic		Replies	Views
Cannot bind por 80 or 443, Windows Docker Desktop docker , windows	3	7097	August 28, 2016
WSL 2 Backend has stopped unexpectedly Docker Desktop windows	1	4623	October 2, 2022
Can't connect to WSL2 based container via the web-browser Docker Desktop linux	13	48059	February 16, 2025
Docker Unable to proxy outside container Docker Hub docker	1	3120	December 12, 2023
Docker Desktop for Windows stuck on "Starting the Docker Engine" Docker Desktop windows	5	8123	May 17, 2025

Why my docker so stupid docker proxy infinity alive

Related topics