From: "Serge E. Hallyn" <serge-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
To: Jun OKAJIMA <okajima-og82NyAXoxRpnGNL948N7c8NsWr+9BEh@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: Container for Amazon EC2?
Date: Wed, 17 Feb 2010 09:36:19 -0600 [thread overview]
Message-ID: <20100217153619.GA23760@hallyn.com> (raw)
In-Reply-To: <2c2629fa1002170723o43aed18as7745b2ce4217474b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
Quoting Jun OKAJIMA (okajima-og82NyAXoxRpnGNL948N7c8NsWr+9BEh@public.gmane.org):
> This is my result.
> I dont know very well about lxc,
> but this is usable?
I'm not sure which you mean as usable: lxc is very usable, and
lets you run multiple application and system containers of various
distros. The lxc-users-5NWGOfrQmneRv+LV9MX5uipxlwaOVQ5f@public.gmane.org mailing list was
recently started to accomodate its growing user base.
The kernel on the ec2 instance, however, is not :)
It might be worth jumping onto #ubuntu-virt and asking whether
they have, or can publish, a kernel with, at the least:
CONFIG_CGROUP_DEVICE=y
CONFIG_CGROUP_FREEZER=y
CONFIG_NAMESPACES=y
CONFIG_UTS_NS=y
CONFIG_IPC_NS=y
CONFIG_USER_NS=y
CONFIG_PID_NS=y
CONFIG_NET_NS=y
CONFIG_VETH=y
CONFIG_MACVLAN=y
CONFIG_BRIDGE=y
CONFIG_DEVPTS_MULTIPLE_INSTANCES=y
Those should be sufficient to start using lxc very nicely
-serge
prev parent reply other threads:[~2010-02-17 15:36 UTC|newest]
Thread overview: 8+ messages / expand[flat|nested] mbox.gz Atom feed top
2010-02-15 10:43 Container for Amazon EC2? Jun OKAJIMA
[not found] ` <2c2629fa1002150243n4c91d93ctee4509912228f3ea-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-15 14:39 ` Serge E. Hallyn
[not found] ` <20100215143905.GD28038-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-17 15:19 ` Serge E. Hallyn
[not found] ` <20100217151943.GA9159-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2010-02-17 15:23 ` Jun OKAJIMA
[not found] ` <2c2629fa1002170723o43aed18as7745b2ce4217474b-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-17 15:31 ` Jun OKAJIMA
[not found] ` <2c2629fa1002170731l4f58f5c7p64caccb8e662d6e5-JsoAwUIsXosN+BqQ9rBEUg@public.gmane.org>
2010-02-17 16:30 ` Serge E. Hallyn
[not found] ` <20100217163029.GA24119-A9i7LUbDfNHQT0dZR+AlfA@public.gmane.org>
2010-02-17 16:39 ` Jun OKAJIMA
2010-02-17 15:36 ` Serge E. Hallyn [this message]
Reply instructions:
You may reply publicly to this message via plain-text email
using any one of the following methods:
* Save the following mbox file, import it into your mail client,
and reply-to-all from there: mbox
Avoid top-posting and favor interleaved quoting:
https://en.wikipedia.org/wiki/Posting_style#Interleaved_style
* Reply using the --to, --cc, and --in-reply-to
switches of git-send-email(1):
git send-email \
--in-reply-to=20100217153619.GA23760@hallyn.com \
--to=serge-a9i7lubdfnhqt0dzr+alfa@public.gmane.org \
--cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
--cc=okajima-og82NyAXoxRpnGNL948N7c8NsWr+9BEh@public.gmane.org \
/path/to/YOUR_REPLY
https://kernel.org/pub/software/scm/git/docs/git-send-email.html
* If your mail client supports setting the In-Reply-To header
via mailto: links, try the mailto: link
Be sure your reply has a Subject: header at the top and a blank line
before the message body.
This is a public inbox, see mirroring instructions
for how to clone and mirror all data and code used for this inbox