Zun

Cannot create container with kata runtime

Bug #1754552 reported by hongbin
6
This bug affects 1 person
Affects Status Importance Assigned to Milestone
Zun
Invalid
Critical
hongbin

Bug Description

This bug was reported by Adams, Eric <email address hidden> . I copied his report to here:

==========================
I am having issues getting kata-runtime to launch a container that actually works. I thought this was working initially but I suspect when I checked the output of “kata-runtime list” I caught it during the microsecond it started to run before it errored out. When I checked “ps aux | grep qemu” it shows qemu is running but it hangs around even after so it starts the hypervisor but fails.

Here is my error from journalctl

Mar 08 15:08:47 container zun-compute[25071]: 2018-03-08 15:08:47.837 ERROR zun.compute.manager [req-1cfb4860-3281-4178-9d2a-e26c6c821eff admin admin] Error occurred while calling Docker start API: Docker internal error: 500 Server Error: Internal Server Error ("OCI runtime create failed: ERROR received from VM agent, control msg received : Could not setup the network: Could not setup network routes: Could not add/replace route dest()/src()/gw(2001:db8::2)/dev(eth0): no route to host: unknown").: DockerErr or: Docker internal error: 500 Server Error: Internal Server Error ("OCI runtime create failed: ERROR received from VM agent, control msg received : Could not setup the network: Could not setup network routes: Could not add/replace route dest()/src()/gw(2001:db8::2)/dev(eth0): no route to host: unknown").
============================

In addition, there are related bugs reported in GitHub:
* https://github.com/clearcontainers/runtime/issues/1060
* https://github.com/kata-containers/runtime/issues/48

hongbin (hongbin034)
Changed in zun:
importance: Undecided → Critical
status: New → Triaged
hongbin (hongbin034)
description: updated
hongbin (hongbin034)
Changed in zun:
assignee: nobody → hongbin (hongbin034)
description: updated
Revision history for this message
hongbin (hongbin034) wrote :

The Kata team reported that this issue was fixed: https://github.com/kata-containers/runtime/issues/48

Changed in zun:
status: Triaged → Invalid
To post a comment you must log in.
This report contains Public information  
Everyone can see this information.

Other bug subscribers

Remote bug watches

Bug watches keep track of this bug in other bug trackers.