From: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+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:19:44 -0600 [thread overview]
Message-ID: <20100217151943.GA9159@us.ibm.com> (raw)
In-Reply-To: <20100215143905.GD28038-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
So I tried running one of the public ubuntu karmic images in
ec2 (ami-bb709dd2). I could sudo apt-get install lxc. The
default kernel (aki-5f15f636) didn't support namespaces. Now
you can specify kernels at boot, but I'm not sure if there is
an easy way to find kernels with specific CONFIG_ options.
I'll let you know if I find one with all namespaces and
veth+bridge+macvlan enabled, bc that would then give you
everything you'd need.
-serge
Quoting Serge E. Hallyn (serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org):
> It's been a little while (probably a year) since I played with
> EC2, but generally the problem is that you don't have much of
> a choice for underlying kernels. So you can't pick vserver/openvz
> kernels, and the available kernels are too old to have containers
> features. As kernels get updated, whether you can use lxc or not
> will only depend on whether CONFIG_{containers} features are compiled
> in.
>
> It couldn't hurt to write the amazon folks and ask about it...
>
> -serge
>
> Quoting Jun OKAJIMA (okajima-og82NyAXoxRpnGNL948N7c8NsWr+9BEh@public.gmane.org):
> > Somebody know any Amazon EC2 Image which
> > supports any container technology?
> > Vserver/LXC/OpenVZ... Any technology is Okay,
> > I want to use pre-created image for EC2.
> >
> > I found many images for Ubuntu 9.10,
> > but it lacks some support for LXC.
> > Fedora12 supports all functions of LXC,
> > but did not find any image.
> >
> > --- Okajima, Jun. Tokyo, Japan.
> > _______________________________________________
> > Containers mailing list
> > Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> > https://lists.linux-foundation.org/mailman/listinfo/containers
> _______________________________________________
> Containers mailing list
> Containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
> https://lists.linux-foundation.org/mailman/listinfo/containers
next prev parent reply other threads:[~2010-02-17 15:19 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 [this message]
[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
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=20100217151943.GA9159@us.ibm.com \
--to=serue-r/jw6+rmf7hqt0dzr+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 an external index of several public inboxes,
see mirroring instructions on how to clone and mirror
all data and code used by this external index.