Xu Wang

OK, will take a look. Thank you

@Chen8132 I checked the code of these two flags, and both designed for **OCI Image format** ```golang Name string `short:"n" long:"name" value-name:"\"\"" description:"Name to use when loading OCI image layout...

These two options are not for the images saved by docker

Did you try using the `-t` option?

try hit the enter key after attach, if your container is launched with `-t`. Sometimes it simply no output after you attached. And could you got output if you exec...

Specific image or no output with any images? And could you get the output with `hyperctl logs`?

hyperd is intended to be deployed on physical machine by default, and it employs hypervisor to provide isolated containers. For running in VMs, you could try to use xenpv driver...

ref https://issues.apache.org/jira/browse/MESOS-3435

@xiaods I watched the issue. Feel free to file issue or submit pr to us. one more thing, @feiskyer is working on implement a hyper driver for kubernetes in repo...

looks like a container name as `c1` had not been cleaned up well... Is this the first time of failure? I guess there were different fail log for the first...