FS#50019 - [docker] Could not run containers based on systemd with default config
Attached to Project:
Community Packages
Opened by Mateusz Marzantowicz (mmarzantowicz) - Monday, 11 July 2016, 13:10 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 26 September 2016, 17:32 GMT
Opened by Mateusz Marzantowicz (mmarzantowicz) - Monday, 11 July 2016, 13:10 GMT
Last edited by Sébastien Luttringer (seblu) - Monday, 26 September 2016, 17:32 GMT
|
Details
Description:
After recent updated, I'm no longer able to run containers managed by systemd (e.g. Fedora 24 with /usr/sbin/init as command to run). I get following result: Failed to determine whether /sys is a mount point: Operation not permitted Failed to determine whether /proc is a mount point: Operation not permitted Failed to determine whether /dev is a mount point: Operation not permitted Failed to determine whether /dev/shm is a mount point: Operation not permitted Failed to determine whether /run is a mount point: Operation not permitted Failed to determine whether /sys/fs/cgroup is a mount point: Operation not permitted Failed to determine whether /sys/fs/cgroup/systemd is a mount point: Operation not permitted [!!!!!!] Failed to mount API filesystems, freezing. Freezing execution. This might be caused by latest addition of libseccomp because on previous docker versions compiled without it, those containers work as expected. Additional info: * package version(s) Name : docker Version : 1:1.11.2-2 Steps to reproduce: Run command: $ docker run --rm -ti -e container=docker -v /sys/fs/cgroup:/sys/fs/cgroup:ro -v /run fedora:24 /usr/sbin/init |
This task depends upon
Closed by Sébastien Luttringer (seblu)
Monday, 26 September 2016, 17:32 GMT
Reason for closing: Not a bug
Monday, 26 September 2016, 17:32 GMT
Reason for closing: Not a bug
1) We disable seccomp?
2) Change the default seccomp profiles to allow systemd required syscall?