-
Notifications
You must be signed in to change notification settings - Fork 70
"Outer" container & Qemu process isolation #127
Comments
From @dlespiau on September 9, 2016 14:14 Adding Anthony to the discussion, he'll probably have some good input for the qemu side of things. |
From @anthonyzxu on September 13, 2016 0:43 Can we run CC inside container? then we can use cgroup ACL for CC. |
From @grahamwhaley on September 13, 2016 9:31 Hi @anthonyzxu Yes, we have considered running QEMU inside a container if that is needed to provide any of the required functionality - if that is the best way to provide it. Although I think we all agree it may 'feel a little odd', using a container space to wrap the VM that is providing a method to run containers in VMs, if there is a feature/method we need that is only really viable (or most efficient/effective) via a container space, then we should probably go that route. |
From @anthonyzxu on September 13, 2016 23:33 https://github.com/rancher/vm Maybe we can leverage their efforts. |
From @anthonyzxu on September 13, 2016 23:35 Seems they use runc to start the VM container |
@jcvenegas - I'm wondering if this issue can be closed? I think we have other proposals for resource management opened, and I'm not sure if we're looking at improved isolation? |
From @dlespiau on September 9, 2016 11:21
Most of the OCI isolation/security features don't directly apply to the qemu process, but to the workload process inside the VM (eg. seccomp filters).
However we want to:
Investigation is needed to:
Copied from original issue: intel/cc-oci-runtime#246
The text was updated successfully, but these errors were encountered: