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
{{ message }}
This repository has been archived by the owner on Sep 4, 2021. It is now read-only.
We should support running containers using libcontainer for the following reasons:
More control over assigned resources (e.g. capabilities, currently hard-coded by libvirt-lxc)
Do away with most of containerinit (containers will be direct children of flynn-host so FDs can be shared in a more conventional way rather than passing them over Unix sockets, and libcontainer does most of the other setup like networking and setting rlimits)
Drop libvirt-lxc as a dependency (this would break in-place updates, so we would either need to keep libvirt-lxc around or not allow users to do an in-place update)
Support running Flynn in Flynn (which would make testing things like cluster backup / restore much easier)
We should support running containers using libcontainer for the following reasons:
flynn-host
so FDs can be shared in a more conventional way rather than passing them over Unix sockets, andlibcontainer
does most of the other setup like networking and setting rlimits)libvirt-lxc
as a dependency (this would break in-place updates, so we would either need to keep libvirt-lxc around or not allow users to do an in-place update)I have made a start on this on the
host-libcontainer-runtime
branch: https://github.com/flynn/flynn/compare/host-libcontainer-runtimeThe text was updated successfully, but these errors were encountered: