Bug 1325466 - Docker container build fails, renders host system unusable. Works without native.cgroupdriver=system
Summary: Docker container build fails, renders host system unusable. Works without nat...
Keywords:
Status: CLOSED INSUFFICIENT_DATA
Alias: None
Product: Fedora
Classification: Fedora
Component: docker
Version: 24
Hardware: Unspecified
OS: Unspecified
unspecified
unspecified
Target Milestone: ---
Assignee: Mrunal Patel
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2016-04-08 23:20 UTC by Matthew Garrett
Modified: 2016-08-19 20:57 UTC (History)
12 users (show)

Fixed In Version:
Doc Type: Bug Fix
Doc Text:
Clone Of:
Environment:
Last Closed: 2016-08-19 20:57:11 UTC
Type: Bug


Attachments (Terms of Use)
Dockerfile triggering the issue (586 bytes, text/plain)
2016-04-08 23:20 UTC, Matthew Garrett
no flags Details

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?


Note You need to log in before you can comment on or make changes to this bug.