Docker Community Forums

Share and learn in the Docker community.

Sytemd error messages "File name too long"


(Sweharris) #1

CentOS 7.4.

Looks like some of the internal filenames generated for k8s are too long

Jan 29 14:44:52 host-172-16-19-230 systemd: Failed to open directory /etc/systemd/system/var-lib-docker-devicemapper-mnt-ca5827128247293cace15cc4347d81691bbc9bc5aa36f0e5f6f352551d79c693-rootfs-hostvar-lib-kubelet-pods-90450ea5\x2d02b8\x2d11e8\x2d9407\x2d0242ac110011-volumes-kubernetes.io\x7esecret-calico\x2dnode\x2dtoken\x2dwv4pg.mount.requires: File name too long

Jan 29 14:44:52 host-172-16-19-230 systemd: Failed to open directory /run/systemd/system/var-lib-docker-devicemapper-mnt-ca5827128247293cace15cc4347d81691bbc9bc5aa36f0e5f6f352551d79c693-rootfs-hostvar-lib-kubelet-pods-90450ea5\x2d02b8\x2d11e8\x2d9407\x2d0242ac110011-volumes-kubernetes.io\x7esecret-calico\x2dnode\x2dtoken\x2dwv4pg.mount.requires: File name too long

Jan 29 14:44:52 host-172-16-19-230 systemd: Failed to open directory /run/systemd/generator/var-lib-docker-devicemapper-mnt-ca5827128247293cace15cc4347d81691bbc9bc5aa36f0e5f6f352551d79c693-rootfs-hostvar-lib-kubelet-pods-90450ea5\x2d02b8\x2d11e8\x2d9407\x2d0242ac110011-volumes-kubernetes.io\x7esecret-calico\x2dnode\x2dtoken\x2dwv4pg.mount.requires: File name too long

Jan 29 14:44:52 host-172-16-19-230 systemd: Failed to open directory /usr/lib/systemd/system/var-lib-docker-devicemapper-mnt-ca5827128247293cace15cc4347d81691bbc9bc5aa36f0e5f6f352551d79c693-rootfs-hostvar-lib-kubelet-pods-90450ea5\x2d02b8\x2d11e8\x2d9407\x2d0242ac110011-volumes-kubernetes.io\x7esecret-calico\x2dnode\x2dtoken\x2dwv4pg.mount.requires: File name too long

Jan 29 14:44:52 host-172-16-19-230 systemd: Failed to open directory /run/systemd/generator.late/var-lib-docker-devicemapper-mnt-ca5827128247293cace15cc4347d81691bbc9bc5aa36f0e5f6f352551d79c693-rootfs-hostvar-lib-kubelet-pods-90450ea5\x2d02b8\x2d11e8\x2d9407\x2d0242ac110011-volumes-kubernetes.io\x7esecret-calico\x2dnode\x2dtoken\x2dwv4pg.mount.requires: File name too long

Jan 29 14:44:52 host-172-16-19-230 systemd: Failed to open directory /etc/systemd/system/var-lib-docker-devicemapper-mnt-ca5827128247293cace15cc4347d81691bbc9bc5aa36f0e5f6f352551d79c693-rootfs-hostvar-lib-kubelet-pods-90450ea5\x2d02b8\x2d11e8\x2d9407\x2d0242ac110011-volumes-kubernetes.io\x7esecret-calico\x2dnode\x2dtoken\x2dwv4pg.mount.requires: File name too long

Jan 29 14:44:52 host-172-16-19-230 systemd: Failed to open directory /run/systemd/system/var-lib-docker-devicemapper-mnt-ca5827128247293cace15cc4347d81691bbc9bc5aa36f0e5f6f352551d79c693-rootfs-hostvar-lib-kubelet-pods-90450ea5\x2d02b8\x2d11e8\x2d9407\x2d0242ac110011-volumes-kubernetes.io\x7esecret-calico\x2dnode\x2dtoken\x2dwv4pg.mount.requires: File name too long

Jan 29 14:44:52 host-172-16-19-230 systemd: Failed to open directory /run/systemd/generator/var-lib-docker-devicemapper-mnt-ca5827128247293cace15cc4347d81691bbc9bc5aa36f0e5f6f352551d79c693-rootfs-hostvar-lib-kubelet-pods-90450ea5\x2d02b8\x2d11e8\x2d9407\x2d0242ac110011-volumes-kubernetes.io\x7esecret-calico\x2dnode\x2dtoken\x2dwv4pg.mount.requires: File name too long

Jan 29 14:44:52 host-172-16-19-230 systemd: Failed to open directory /usr/lib/systemd/system/var-lib-docker-devicemapper-mnt-ca5827128247293cace15cc4347d81691bbc9bc5aa36f0e5f6f352551d79c693-rootfs-hostvar-lib-kubelet-pods-90450ea5\x2d02b8\x2d11e8\x2d9407\x2d0242ac110011-volumes-kubernetes.io\x7esecret-calico\x2dnode\x2dtoken\x2dwv4pg.mount.requires: File name too long

Jan 29 14:44:52 host-172-16-19-230 systemd: Failed to open directory /run/systemd/generator.late/var-lib-docker-devicemapper-mnt-ca5827128247293cace15cc4347d81691bbc9bc5aa36f0e5f6f352551d79c693-rootfs-hostvar-lib-kubelet-pods-90450ea5\x2d02b8\x2d11e8\x2d9407\x2d0242ac110011-volumes-kubernetes.io\x7esecret-calico\x2dnode\x2dtoken\x2dwv4pg.mount.requires: File name too long

(Matt Bentley) #2

I’ve also come across that and have opened an issue internally to track that down.