Container is causing mount point 'Deactivated successfully' spam in systemd log

[XxAcielxX]

Support guidelines

• I've read the support guidelines

I've found a bug and checked that ...

• ... the documentation does not mention anything about my problem
• ... there are no open or closed issues that are related to my problem

Description

When running the container this error is being spammed in my systemd log.

Expected behaviour

The error should not occur and be spammed at all.

Actual behaviour

This error is happening

Feb 29 13:40:38 server systemd[1]: run-docker-runtime\x2drunc-moby-52b515d4abad93429b47d31f6ae761627d3a9eaa2ce778b83705badc1af7a2d8-runc.jRgWsb.mount: Deactivated successfully.
Feb 29 13:44:39 server systemd[1]: run-docker-runtime\x2drunc-moby-52b515d4abad93429b47d31f6ae761627d3a9eaa2ce778b83705badc1af7a2d8-runc.b18vgx.mount: Deactivated successfully.
Feb 29 13:46:09 server systemd[1]: run-docker-runtime\x2drunc-moby-52b515d4abad93429b47d31f6ae761627d3a9eaa2ce778b83705badc1af7a2d8-runc.1A6mVn.mount: Deactivated successfully.
Feb 29 13:47:09 server systemd[1]: run-docker-runtime\x2drunc-moby-52b515d4abad93429b47d31f6ae761627d3a9eaa2ce778b83705badc1af7a2d8-runc.NlQ1g3.mount: Deactivated successfully.
Feb 29 13:47:39 server systemd[1]: run-docker-runtime\x2drunc-moby-52b515d4abad93429b47d31f6ae761627d3a9eaa2ce778b83705badc1af7a2d8-runc.yd3WZV.mount: Deactivated successfully.
Feb 29 13:48:10 server systemd[1]: run-docker-runtime\x2drunc-moby-52b515d4abad93429b47d31f6ae761627d3a9eaa2ce778b83705badc1af7a2d8-runc.orGghr.mount: Deactivated successfully.
Feb 29 13:48:40 server systemd[1]: run-docker-runtime\x2drunc-moby-52b515d4abad93429b47d31f6ae761627d3a9eaa2ce778b83705badc1af7a2d8-runc.i3LSQU.mount: Deactivated successfully.

This keeps happening 24/7 at random intervals.

Steps to reproduce

1. Run the container
2. Wait, and check sudo journalctl -n 50 -f

Docker info

Client: Docker Engine - Community
 Version:    25.0.3
 Context:    default
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.12.1
    Path:     /usr/libexec/docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.24.5
    Path:     /usr/libexec/docker/cli-plugins/docker-compose

Server:
 Containers: 19
  Running: 18
  Paused: 0
  Stopped: 1
 Images: 22
 Server Version: 25.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: io.containerd.runc.v2 runc
 Default Runtime: runc
 Init Binary: docker-init
 containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc version: v1.1.12-0-g51d5e94
 init version: de40ad0
 Security Options:
  apparmor
  seccomp
   Profile: builtin
  cgroupns
 Kernel Version: 6.1.0-18-amd64
 Operating System: Debian GNU/Linux 12 (bookworm)
 OSType: linux
 Architecture: x86_64
 CPUs: 4
 Total Memory: 7.633GiB
 Name: server
 ID: REDACTED
 Docker Root Dir: /var/lib/docker
 Debug Mode: false
 Experimental: false
 Insecure Registries:
  127.0.0.0/8
 Live Restore Enabled: false

Docker Compose config

...
  samba:
    image: crazymax/samba
    container_name: samba
    network_mode: host
    mem_limit: 512m
    environment:
      - TZ=${TZ}
      - SAMBA_LOG_LEVEL=0
      - LOG_LEVEL=debug
    volumes:
      - ${APP_CONF}/samba:/data
      - /home/aciel:/samba/server/aciel
      - /app_conf:/samba/server/app_conf
      - ${WDC}:/samba/server/WDC
      - ${MEDIA}:/samba/server/Media
    restart: always

Logs

Can't get debug log

Additional info

I have same setup on a Raspberry Pi 4 8GB, it does the exact same thing as well.