CloudFoundry to re-base its warden component on libcontainer

137 views
Skip to first unread message

Glyn Normington

unread,
Jun 19, 2014, 8:30:29 AM6/19/14
to docke...@googlegroups.com

Victor Marmol

unread,
Jun 19, 2014, 11:55:44 AM6/19/14
to Glyn Normington, docker-dev
Great to hear Glyn! Happy to welcome our new contributors from CloudFoundry to libcontainer :) unifying these stacks will help us move forward much faster.


On Thu, Jun 19, 2014 at 5:30 AM, Glyn Normington <gnorm...@gopivotal.com> wrote:

--
You received this message because you are subscribed to the Google Groups "docker-dev" group.
To unsubscribe from this group and stop receiving emails from it, send an email to docker-dev+...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Glyn Normington

unread,
Oct 27, 2014, 5:52:08 AM10/27/14
to docke...@googlegroups.com, gnorm...@gopivotal.com
We have found that Warden's features are hard to implement on top of libcontainer, mainly because of the way libcontainer manages user processes. So we have decided to defer development with libcontainer until such time as the implementation stabilises (i.e. after libct is integrated) at which point it may be worth having another look.

We are, however, planning to reuse some of libcontainer's Go packages, specifically netlink, which match our requirements.

(Please note that Garden, the Go variant of Warden, already supports using Docker images as container root file systems.)

On Thursday, June 19, 2014 4:55:44 PM UTC+1, Victor Marmol wrote:
Great to hear Glyn! Happy to welcome our new contributors from CloudFoundry to libcontainer :) unifying these stacks will help us move forward much faster.
On Thu, Jun 19, 2014 at 5:30 AM, Glyn Normington <gnorm...@gopivotal.com> wrote:

--
Reply all
Reply to author
Forward
0 new messages