A imagem do docker do nginx faz com que comandos no host sejam paralisados

docker container run -d -p 2345:80 nginx

funciona quase como esperado. Leva cerca de 1s até que o nginx esteja disponível. No entanto, assim que ele foi iniciado, comandos como tope htopparar completamente o anfitrião. São necessários mais de três minutos para mostrar sua saída. O mesmo é verdade para docker container top. Assim que eu parar o último container com nginx, esses comandos funcionam rapidamente como de costume. Outros contêineres docker não apresentam esse problema (tentei redis e postgres, por exemplo).

docker version
Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:23:03 2018
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:25:29 2018
  OS/Arch:          linux/amd64
  Experimental:     false

Eu rebaixei de 18.09 para o 18.06 mais estável, mas isso não ajudou.

A máquina está inativa após a inicialização do nginx (memória, cpu e i / o são muito baixas).

O problema se reproduz toda vez.

O host executa a versão 7.5.1804 do CentOS Linux (Core)

uname -r

3.10.0-862.11.6.el7.x86_64

Sou grato por quaisquer dicas, já que confio no nginx para compor redox docker-red.

docker stats

CONTAINER ID        NAME                CPU %               MEM USAGE / LIMIT     MEM %               NET I/O             BLOCK I/O           PIDS
5c6ac577dc09        epic_benz           0.00%               1.352MiB / 15.51GiB   0.01%               648B / 0B           0B / 0B             2

Editar 2018-10-02

Note que eu não consegui reproduzir o problema no Ubuntu Linux 18.04 ou no KDE Neon baseado no Ubuntu 16.04. /var/log/messages(corresponde aos /var/log/syslogsistemas debian) mostra

Oct  2 09:17:52 computer kernel: docker0: port 1(veth7d5218b) entered blocking state
Oct  2 09:17:52 computer kernel: docker0: port 1(veth7d5218b) entered disabled state
Oct  2 09:17:52 computer kernel: device veth7d5218b entered promiscuous mode
Oct  2 09:17:52 computer kernel: IPv6: ADDRCONF(NETDEV_UP): veth7d5218b: link is not ready
Oct  2 09:17:52 computer kernel: docker0: port 1(veth7d5218b) entered blocking state
Oct  2 09:17:52 computer kernel: docker0: port 1(veth7d5218b) entered forwarding state
Oct  2 09:17:52 computer kernel: docker0: port 1(veth7d5218b) entered disabled state
Oct  2 09:17:52 computer NetworkManager[741]: <info>  [1538464672.3371] manager: (veth4e56e00): new Veth device (/org/freedesktop/NetworkManager/Devices/123)
Oct  2 09:17:52 computer NetworkManager[741]: <info>  [1538464672.3386] manager: (veth7d5218b): new Veth device (/org/freedesktop/NetworkManager/Devices/124)
Oct  2 09:17:52 computer dockerd: time="2018-10-02T09:17:52+02:00" level=info msg="shim docker-containerd-shim started" address="/containerd-shim/moby/6f10f1290f60d75ea6848347868c91ab1d744c4b3d57c460099bb283a2eeed1b/shim.sock" debug=false pid=9211
Oct  2 09:17:53 computer kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth7d5218b: link becomes ready
Oct  2 09:17:53 computer kernel: docker0: port 1(veth7d5218b) entered blocking state
Oct  2 09:17:53 computer kernel: docker0: port 1(veth7d5218b) entered forwarding state
Oct  2 09:17:53 computer NetworkManager[741]: <info>  [1538464673.4452] device (veth7d5218b): carrier: link connected
Oct  2 09:17:53 computer NetworkManager[741]: <info>  [1538464673.4453] device (docker0): carrier: link connected

durante a inicialização e

Oct  2 09:20:48 computer dockerd: time="2018-10-02T09:20:48+02:00" level=info msg="shim reaped" id=6f10f1290f60d75ea6848347868c91ab1d744c4b3d57c460099bb283a2eeed1b
Oct  2 09:20:48 computer dockerd: time="2018-10-02T09:20:48.478545725+02:00" level=info msg="ignoring event" module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Oct  2 09:20:48 computer kernel: docker0: port 1(veth7d5218b) entered disabled state
Oct  2 09:20:48 computer NetworkManager[741]: <info>  [1538464848.5327] manager: (veth4e56e00): new Veth device (/org/freedesktop/NetworkManager/Devices/125)
Oct  2 09:20:48 computer kernel: docker0: port 1(veth7d5218b) entered disabled state
Oct  2 09:20:48 computer kernel: device veth7d5218b left promiscuous mode
Oct  2 09:20:48 computer kernel: docker0: port 1(veth7d5218b) entered disabled state
Oct  2 09:20:48 computer NetworkManager[741]: <info>  [1538464848.5444] device (veth7d5218b): released from master device docker0

durante o desligamento.