-
Notifications
You must be signed in to change notification settings - Fork 18.9k
Description
Description
After I updated to Docker 27.0.3 (I do not remember what was the older version, sorry, I upgraded my dedicated servers when the RegreSSHion exploit happened, but technically the older version is a version between 10/01/2024 (when the system was installed) and 01/07/2024 (when I upgraded all packages)) the dockerd daemon is leaking memory like crazy, in two of my dedicated servers dockerd ends up eating so much memory that containers end up getting OOM'd by the system
If I restart Docker, the dockerd memory usage drops to ~200MB, and then keeps increasing and increasing and increasing...
Reproduce
I don't know how to reproduce this yet
Expected behavior
That dockerd does not eating up so much memory.
docker version
Docker version 27.0.3, build 7d4bcd8docker info
Client: Docker Engine - Community
Version: 27.0.3
Context: default
Debug Mode: false
Plugins:
buildx: Docker Buildx (Docker Inc.)
Version: v0.15.1
Path: /usr/libexec/docker/cli-plugins/docker-buildx
compose: Docker Compose (Docker Inc.)
Version: v2.28.1
Path: /usr/libexec/docker/cli-plugins/docker-compose
Server:
Containers: 68
Running: 68
Paused: 0
Stopped: 0
Images: 41
Server Version: 27.0.3
Storage Driver: overlay2
Backing Filesystem: extfs
Supports d_type: true
Using metacopy: false
Native Overlay Diff: true
userxattr: false
Logging Driver: local
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: runc io.containerd.runc.v2
Default Runtime: runc
Init Binary: docker-init
containerd version: ae71819c4f5e67bb4d5ae76a6b735f29cc25774e
runc version: v1.1.13-0-g58aa920
init version: de40ad0
Security Options:
apparmor
seccomp
Profile: builtin
cgroupns
Kernel Version: 6.5.0-41-generic
Operating System: Ubuntu 22.04.4 LTS
OSType: linux
Architecture: x86_64
CPUs: 16
Total Memory: 125.7GiB
Name: saiyan-seeker
ID: 3ae68731-57aa-49b8-bc88-c007cbcc3059
Docker Root Dir: /var/lib/docker
Debug Mode: false
Experimental: false
Insecure Registries:
127.0.0.0/8
Live Restore Enabled: false
Default Address Pools:
Base: 172.16.0.0/12, Size: 20
Base: 192.168.0.0/16, Size: 24Additional Info
Yeah, this issue doesn't really help a lot to figure out what is actually the issue... When I was looking at other comments, I found out that there is a way to create a heap dump of the dockerd process, but the link on how to do it is unavailable and it a mirror is not available on the Wayback Machine, so I wonder if someone has a working link about how to do it? #39916 (comment)
