Failed to run container

237 views
Skip to first unread message

qiong lin

unread,
Jul 29, 2020, 6:18:41 AM7/29/20
to gVisor Users [Public]

[root@vm-05-187 moby]# docker run --runtime=runsc --rm hello-world
docker: Error response from daemon: OCI runtime create failed: unable to retrieve OCI runtime error (open /run/containerd/io.containerd.runtime.v1.linux/moby/1e6223a7cdb30e0a4dd47d17de60212b798899864819993d881c796a4521914e/log.json: no such file or directory): /usr/local/bin/runsc did not terminate sucessfully: unknown.


Other useful information:
[root@vm-05-187 moby]# uname -a
Linux vm-05-187 5.7.7-1.el7.elrepo.x86_64 #1 SMP Wed Jul 1 11:53:16 EDT 2020 x86_64 x86_64 x86_64 GNU/Linux

[root@vm-05-187 moby]# docker -v
Docker version 19.03.12, build 48a66213fe 

Fabricio Voznika

unread,
Jul 29, 2020, 7:38:14 PM7/29/20
to qiong lin, gVisor Users [Public]
Hmm, not sure what's happening. Can you please collect debug logs (https://gvisor.dev/docs/user_guide/debugging/) and send them to us?

--
You received this message because you are subscribed to the Google Groups "gVisor Users [Public]" group.
To unsubscribe from this group and stop receiving emails from it, send an email to gvisor-users...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/gvisor-users/8610849f-782b-4cb6-adf8-6d4438936efbn%40googlegroups.com.

Ian Lewis

unread,
Jul 29, 2020, 10:47:11 PM7/29/20
to Fabricio Voznika, qiong lin, gVisor Users [Public]
Hi,

What version of Linux are you using? You may be using an older version of Linux.

You also might check to make sure that the runsc binary has the right permissions bits but I think it's the issue above.



--

Ian Lewis | Developer Advocate | ianl...@google.com | +81 (03)4540-2465

Ian Lewis

unread,
Jul 30, 2020, 12:22:28 AM7/30/20
to Fabricio Voznika, qiong lin, gVisor Users [Public]
Ah, you did give us the Linux version and that seems ok. It very much looks like the memfd_create issue though. This looks like it's a CentOS kernel? maybe memfd_create isn't supported even though it's a 5.x series kernel?

Anyway, as Fabricio said, debug logs would be helpful for finding the right cause.
Reply all
Reply to author
Forward
0 new messages