Run-docker-runtime mount succeed messages flood log

Ask the Community Password Manager
1

I’d appreciate if somebody could tell me how to reduce the successfull log messages.

Apr  1 08:09:07 mail1 systemd[2310904]: run-docker-runtime\x2drunc-moby-3b4b37594eab1a84a822d9f8f1eb824220d32829367a7776606aa13d49177e6f-runc.r7XKw9.mount: Succeeded.
Apr  1 08:09:07 mail1 systemd[2332017]: run-docker-runtime\x2drunc-moby-3b4b37594eab1a84a822d9f8f1eb824220d32829367a7776606aa13d49177e6f-runc.r7XKw9.mount: Succeeded.
Apr  1 08:09:07 mail1 systemd[1]: run-docker-runtime\x2drunc-moby-3b4b37594eab1a84a822d9f8f1eb824220d32829367a7776606aa13d49177e6f-runc.r7XKw9.mount: Succeeded.
Apr  1 08:09:09 mail1 systemd[2332017]: run-docker-runtime\x2drunc-moby-4cec8f350a08d929ff66d0916758ea91504b45e01edcb4d15b1d5c96d6f8ef6f-runc.BmoldA.mount: Succeeded.
Apr  1 08:09:09 mail1 systemd[2310904]: run-docker-runtime\x2drunc-moby-4cec8f350a08d929ff66d0916758ea91504b45e01edcb4d15b1d5c96d6f8ef6f-runc.BmoldA.mount: Succeeded.
Apr  1 08:09:09 mail1 systemd[1]: run-docker-runtime\x2drunc-moby-4cec8f350a08d929ff66d0916758ea91504b45e01edcb4d15b1d5c96d6f8ef6f-runc.BmoldA.mount: Succeeded.
Apr  1 08:09:18 mail1 systemd[2310904]: run-docker-runtime\x2drunc-moby-6047b162960774cfb3eee5a85e47b44ce66af45ec033ba4b2e55c3af1419514d-runc.GQJD5M.mount: Succeeded.
Apr  1 08:09:18 mail1 systemd[2332017]: run-docker-runtime\x2drunc-moby-6047b162960774cfb3eee5a85e47b44ce66af45ec033ba4b2e55c3af1419514d-runc.GQJD5M.mount: Succeeded.
Apr  1 08:09:18 mail1 systemd[1]: run-docker-runtime\x2drunc-moby-6047b162960774cfb3eee5a85e47b44ce66af45ec033ba4b2e55c3af1419514d-runc.GQJD5M.mount: Succeeded.

My (standard) install looks likes this

Client:
 Context:    default
 Debug Mode: false
 Plugins:
  app: Docker App (Docker Inc., v0.9.1-beta3)
  buildx: Docker Buildx (Docker Inc., v0.8.1-docker)
  scan: Docker Scan (Docker Inc., v0.17.0)

Server:
 Containers: 11
  Running: 11
  Paused: 0
  Stopped: 0
 Images: 14
 Server Version: 20.10.14
 Storage Driver: overlay2
  Backing Filesystem: extfs
  Supports d_type: true
  Native Overlay Diff: true
  userxattr: false
 Logging Driver: local
 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: io.containerd.runc.v2 io.containerd.runtime.v1.linux runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: 3df54a852345ae127d1fa3092b95168e4a88e2f8
 runc version: v1.0.3-0-gf46b6ba
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: default
 Kernel Version: 5.4.0-105-generic
 Operating System: Ubuntu 20.04.4 LTS
 OSType: linux
 Architecture: x86_64
 CPUs: 8
 Total Memory: 29.39GiB
 Name: mail1
 ID: S4LD:2QAM:TYLI:OIXY:WPXJ:ON5D:YROD:SPSA:XH3L:AJ6Y:QGZ5:3XHR
 Docker Root Dir: /home/docker-data
 Debug Mode: false
 Registry: https://index.docker.io/v1/
 Labels:
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

WARNING: No swap limit support
2

While this post https://stackoverflow.com/questions/63622619/docker-flooding-syslog-with-run-docker-runtime-logs suggest how to stop the messages, I don’t understand why the app constantly mounts/remounts.

3

Looks like this is Healthcheck related https://github.com/docker/for-linux/issues/679.

Not sure what the impact on the system is given that the mounts seems to happen constantly