You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Environment
#cat /etc/centos-release
CentOS release 6.7 (Final)
#uname -a
Linux machinename 2.6.32-573.el6.x86_64 #1 SMP Thu Jul 23 15:44:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
#go version
go version go1.7.4 linux/amd64
#runc --version
runc version 1.0.0-rc2
commit: eedebb8
spec: 1.0.0-rc3
Issue
The issue is we cannot run a container using runc. It throws the following exception
#/usr/local/sbin/runc run --no-new-keyring testcontainer container_linux.go:247: starting container process caused "write parent: broken pipe"
#/usr/local/sbin/runc run testcontainer container_linux.go:247: starting container process caused "write parent: broken pipe"
Figured out the fix.
There might be 2 issues that you need to fix
Your runc binary was built with some argument like ‘selinux’ which is no longer compatible to your version. Rather building runc with args you should be using make BUILDTAGS=’’ (empty args)
If you still see the issue the problem might be because of cgroup. Try to start the service by executing
$ Service cgconfig start
Environment
#cat /etc/centos-release
CentOS release 6.7 (Final)
#uname -a
Linux machinename 2.6.32-573.el6.x86_64 #1 SMP Thu Jul 23 15:44:03 UTC 2015 x86_64 x86_64 x86_64 GNU/Linux
#go version
go version go1.7.4 linux/amd64
#runc --version
runc version 1.0.0-rc2
commit: eedebb8
spec: 1.0.0-rc3
Issue
The issue is we cannot run a container using runc. It throws the following exception
#/usr/local/sbin/runc run --no-new-keyring testcontainer
container_linux.go:247: starting container process caused "write parent: broken pipe"
#/usr/local/sbin/runc run testcontainer
container_linux.go:247: starting container process caused "write parent: broken pipe"
Attached config.json file
runc-config.txt
Any suggestion will indeed be helpful
The text was updated successfully, but these errors were encountered: