Closed alexcpn closed 4 years ago
Hi,
The problem is likely that the runsc binary doesn't have the right permissions.
sudo chown root:root /path/to/runsc
sudo chmod 0755 /path/to/runsc
Let me know if that fixes it.
Thanks I tried that, did not help. I guess root cause is linux version
We require a Linux 3.17+ kernel. It looks like you are on 3.10. https://github.com/google/gvisor/issues/55#issuecomment-390713423
Mine is Centos which is on 3.10 uname -r 3.10.0-957.27.2.el7.x86_64
Thanks
@alexcpn Ok, thanks for the follow up!
I followed the instruction here https://github.com/google/gvisor-containerd-shim/blob/master/docs/runtime-handler-shim-v2-quickstart.md
( Installed continerd, conteinerd shim, and runsc - all are in the path, service is running)
I am getting the following error
More logs
Note - with runc I am able to start the container (not sure if it is some permission issue?) sudo crictl -D runp --runtime runc sandbox.json