DescriptionMatthew Garrett
2016-04-08 23:20:30 UTC
Created attachment 1145310[details]
Dockerfile triggering the issue
If I build the attached dockerfile, Docker fails with:
Step 5 : RUN chmod a+rx /hyperkube
---> Running in 672c655a7194
Container command not found or does not exist.
If I run the same job again, it fails in an identical way but this time leaves a namespaced version of /proc mounted on top of the host /proc. Since /proc/self no longer links to anything, everything is broken. Removing --exec-opt native.cgroupdriver=systemd from the systemd unit file results in things working as expected.
hyperkube is simply a go binary built as part of the kubernetes build - I don't think there's anything special about it.
Created attachment 1145310 [details] Dockerfile triggering the issue If I build the attached dockerfile, Docker fails with: Step 5 : RUN chmod a+rx /hyperkube ---> Running in 672c655a7194 Container command not found or does not exist. If I run the same job again, it fails in an identical way but this time leaves a namespaced version of /proc mounted on top of the host /proc. Since /proc/self no longer links to anything, everything is broken. Removing --exec-opt native.cgroupdriver=systemd from the systemd unit file results in things working as expected. hyperkube is simply a go binary built as part of the kubernetes build - I don't think there's anything special about it.