Netdata Community

Netdata Container Falies to Start

Environment

CentOS 8
Docker Version 20.10.7 (CE)
Containerd: 1.4.6
run: 1.0.0-rc95
docker-init: 0.19.0

Problem/Question

My container will not start, it constantly restarts and errors with the following message:

Jun  6 13:52:46 plex kernel: XFS (dm-8): Mounting V5 Filesystem
Jun  6 13:52:46 plex kernel: XFS (dm-8): Ending clean mount
Jun  6 13:52:46 plex kernel: br-eda9ac59b398: port 3(veth17b2e21) entered blocking state
Jun  6 13:52:46 plex kernel: br-eda9ac59b398: port 3(veth17b2e21) entered disabled state
Jun  6 13:52:46 plex kernel: device veth17b2e21 entered promiscuous mode
Jun  6 13:52:46 plex kernel: IPv6: ADDRCONF(NETDEV_UP): veth17b2e21: link is not ready
Jun  6 13:52:46 plex kernel: br-eda9ac59b398: port 3(veth17b2e21) entered blocking state
Jun  6 13:52:46 plex kernel: br-eda9ac59b398: port 3(veth17b2e21) entered forwarding state
Jun  6 13:52:46 plex systemd-udevd[148687]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun  6 13:52:46 plex kernel: br-eda9ac59b398: port 3(veth17b2e21) entered disabled state
Jun  6 13:52:46 plex systemd-udevd[148688]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun  6 13:52:46 plex NetworkManager[1152]: <info>  [1623001966.1186] manager: (vethb47ca2a): new Veth device (/org/freedesktop/NetworkManager/Devices/77)
Jun  6 13:52:46 plex NetworkManager[1152]: <info>  [1623001966.1203] manager: (veth17b2e21): new Veth device (/org/freedesktop/NetworkManager/Devices/78)
Jun  6 13:52:46 plex containerd[1266]: time="2021-06-06T13:52:46.194133912-04:00" level=info msg="starting signal loop" namespace=moby path=/run/containerd/io.containerd.runtime.v2.task/moby/4dee1a5bbf806fe81d6dd02125ac074cd8f0ba3c02cb5e6263145e867310969f pid=148721
Jun  6 13:52:46 plex kernel: eth0: renamed from vethb47ca2a
Jun  6 13:52:46 plex kernel: IPv6: ADDRCONF(NETDEV_CHANGE): veth17b2e21: link becomes ready
Jun  6 13:52:46 plex kernel: br-eda9ac59b398: port 3(veth17b2e21) entered blocking state
Jun  6 13:52:46 plex kernel: br-eda9ac59b398: port 3(veth17b2e21) entered forwarding state
Jun  6 13:52:46 plex NetworkManager[1152]: <info>  [1623001966.3948] device (veth17b2e21): carrier: link connected
Jun  6 13:52:47 plex dockerd[51989]: time="2021-06-06T13:52:47.026947632-04:00" level=info msg="ignoring event" container=4dee1a5bbf806fe81d6dd02125ac074cd8f0ba3c02cb5e6263145e867310969f module=libcontainerd namespace=moby topic=/tasks/delete type="*events.TaskDelete"
Jun  6 13:52:47 plex containerd[1266]: time="2021-06-06T13:52:47.026990611-04:00" level=info msg="shim disconnected" id=4dee1a5bbf806fe81d6dd02125ac074cd8f0ba3c02cb5e6263145e867310969f
Jun  6 13:52:47 plex containerd[1266]: time="2021-06-06T13:52:47.027054722-04:00" level=error msg="copy shim log" error="read /proc/self/fd/22: file already closed"
Jun  6 13:52:47 plex kernel: vethb47ca2a: renamed from eth0
Jun  6 13:52:47 plex NetworkManager[1152]: <info>  [1623001967.0580] manager: (vethb47ca2a): new Veth device (/org/freedesktop/NetworkManager/Devices/79)
Jun  6 13:52:47 plex kernel: br-eda9ac59b398: port 3(veth17b2e21) entered disabled state
Jun  6 13:52:47 plex systemd-udevd[148849]: link_config: autonegotiation is unset or enabled, the speed and duplex are not writable.
Jun  6 13:52:47 plex kernel: br-eda9ac59b398: port 3(veth17b2e21) entered disabled state
Jun  6 13:52:47 plex kernel: device veth17b2e21 left promiscuous mode
Jun  6 13:52:47 plex kernel: br-eda9ac59b398: port 3(veth17b2e21) entered disabled state
Jun  6 13:52:47 plex NetworkManager[1152]: <info>  [1623001967.0728] device (veth17b2e21): released from master device br-eda9ac59b398
Jun  6 13:52:47 plex systemd[6716]: run-docker-netns-cfa4cc6e9102.mount: Succeeded.
Jun  6 13:52:47 plex systemd[6716]: home-plex-containers-4dee1a5bbf806fe81d6dd02125ac074cd8f0ba3c02cb5e6263145e867310969f-mounts-shm.mount: Succeeded.
Jun  6 13:52:47 plex systemd[6716]: home-plex-devicemapper-mnt-48ae784cf49106b3c07fc65e9e01c628a79307d22120186c8484275482579086.mount: Succeeded.
Jun  6 13:52:47 plex kernel: XFS (dm-8): Unmounting Filesystem

What I expected to happen

container to start, like it has for some time. I’m not sure if it was an update to CentOS8 that caused it, or a new deployment of the container. I’m searched for a while but finding 5-6 year old errors that say it was patched and fixed but aren’t related to net data.

my docker-compose for starting net data:

netdata:
    image: netdata/netdata
    container_name: netdata
    hostname: plex.nomorestars.local # set to fqdn of host
    ports:
      - 19999:19999
    restart: unless-stopped
    cap_add:
      - SYS_PTRACE
    security_opt:
      - apparmor:unconfined
    volumes:
      - netdataconfig:/etc/netdata
      - netdatalib:/var/lib/netdata
      - netdatacache:/var/cache/netdata
      - /etc/passwd:/host/etc/passwd:ro
      - /etc/group:/host/etc/group:ro
      - /proc:/host/proc:ro
      - /sys:/host/sys:ro
      - /etc/os-release:/host/etc/os-release:ro

Hey @trekkie,

Although I am not proficient with plex, having used the container over the weekend and knowing a bit about containers, I think it’s not related to Netdata.

Due to the tech, I am almost certain that it should just “play”, since the netdata environment doesn’t change from container engine to container engine.

That being said, an error line in the code you supplied mentions that it was not possible to read proc. Can you verify that the docker runtime that you use allows this volume mount? - /proc:/host/proc:ro

For example, in balena, although it’s docker-container, in order to give access to proc, you have to pass a label.

thanks for pointing me in a direction, i’ll look into it. I’m relatively new to docker as well.