You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Recently, I have found a project (a container runtime) called Sysbox which can run "VM workloads" inside a Docker container. So the sys container managed by the Sysbox can run e.g. systemd, Kubernetes inside a Docker container. This startup is recently acquired by the Docker company. I would like to check this runc and use it as the runtime to run outside Docker containers in the comnetsemu. This can replace the current very limited and insecure sibling container mechanism used by comnetsemu. With this new runtime, it is possible to use comnetsemu to emulate a network of e.g. multiple Kubernetes clusters without using e.g. nested VM virtualization.
The text was updated successfully, but these errors were encountered:
Recently, I have found a project (a container runtime) called Sysbox which can run "VM workloads" inside a Docker container. So the sys container managed by the Sysbox can run e.g. systemd, Kubernetes inside a Docker container. This startup is recently acquired by the Docker company. I would like to check this runc and use it as the runtime to run outside Docker containers in the comnetsemu. This can replace the current very limited and insecure sibling container mechanism used by comnetsemu. With this new runtime, it is possible to use comnetsemu to emulate a network of e.g. multiple Kubernetes clusters without using e.g. nested VM virtualization.
The text was updated successfully, but these errors were encountered: