Bug 1325466

Summary: Docker container build fails, renders host system unusable. Works without native.cgroupdriver=system
Product: [Fedora] Fedora Reporter: Matthew Garrett <mjg59>
Component: dockerAssignee: Mrunal Patel <mpatel>
Status: CLOSED INSUFFICIENT_DATA QA Contact: Fedora Extras Quality Assurance <extras-qa>
Severity: unspecified Docs Contact:
Priority: unspecified    
Version: 24CC: adimania, admiller, amurdaca, dwalsh, ichavero, jcajka, jchaloup, lsm5, marianne, miminar, nalin, vbatts
Target Milestone: ---   
Target Release: ---   
Hardware: Unspecified   
OS: Unspecified   
Whiteboard:
Fixed In Version: Doc Type: Bug Fix
Doc Text:
Story Points: ---
Clone Of: Environment:
Last Closed: 2016-08-19 20:57:11 UTC Type: Bug
Regression: --- Mount Type: ---
Documentation: --- CRM:
Verified Versions: Category: ---
oVirt Team: --- RHEL 7.3 requirements from Atomic Host:
Cloudforms Team: --- Target Upstream Version:
Attachments:
Description Flags
Dockerfile triggering the issue none

Description Matthew 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.

Comment 1 Daniel Walsh 2016-06-03 19:01:18 UTC
mrunal have you made any progress on this?

Comment 2 Antonio Murdaca 2016-06-12 17:51:41 UTC
Matthew which version of the docker rpm were you running?