-
Notifications
You must be signed in to change notification settings - Fork 41.3k
Closed
Labels
area/kubeletlifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.
Description
version: kubernetes-v1.4.0
OS: RHEL 7.1
cloud-provider: baremetal/''
docker version: 1.12.1
noticing below error log in kubelet logs every 5 mins:
E1004 23:56:49.188958 8353 container_manager_linux.go:567] error opening pid file /run/docker/libcontainerd/docker-containerd.pid: open /run/docker/libcontainerd/docker-containerd.pid: no such file or directory
in our setup, docker-containerd pid is in /var/run/docker/libcontainerd/docker-containerd.pid
. Since the code seems to fallback to pidof/procfs.pid
, does this needs to be logged at ERROR level?
Metadata
Metadata
Assignees
Labels
area/kubeletlifecycle/rottenDenotes an issue or PR that has aged beyond stale and will be auto-closed.Denotes an issue or PR that has aged beyond stale and will be auto-closed.sig/nodeCategorizes an issue or PR as relevant to SIG Node.Categorizes an issue or PR as relevant to SIG Node.