[Lxc-users] fedora template

[Ramez Hanna]

On Wed, Mar 30, 2011 at 11:10 AM, Ramez Hanna <rhanna at informatiq.org> wrote:

> On Wed, Mar 30, 2011 at 2:19 AM, Serge E. Hallyn <serge.hallyn at ubuntu.com>wrote:
>
>> Quoting Ramez Hanna (rhanna at informatiq.org):
>> > I have been working on a fedora template that actually works
>> > febootstrap is not anymore producing fedora rootfs but rather a minimal
>>
>> Really, febootstrap can't be used to create a rootfs at all any more?
>>
> yes as mentioned here http://people.redhat.com/~rjones/febootstrap/
> --quote--
> febootstrap 3.x is a complete rewrite. febootstrap 2.x could only build
> Fedora distributions. This version can build many varieties of Linux
> distros. 3.x only builds supermin appliances, it does not build chroots.
> --unquote--
>
>>
>> > fedora appliance
>> > my solution works by using yum instead, but I am facing a really weired
>> > situation
>> > whenever i start my fedora container, it would actually try to change
>> the
>> > init level of the host
>> > host is f14 and container is f14
>> > could anyone shed some light on how the container is actually being
>> > isolated, so i can start from there
>> > or how can i debug?
>> > script used to create the container attached, it is based on the current
>> > template with a few modifications here and there
>>
>> Note that for me to use this template on ubuntu, I have to specify '-R
>> 14',
>> but lxc-create doesn't allow me to forward that option.  So I have to
>> first create the config file and then run fedora2 by hand.  After that,
>> for some reason I still have no actual rootfs :(.
>>
> this is a typo in the script i fixed it, find the latest version attached
>
>>
>> As for trouble with init - is your fedora using systemd?  How does it
>> actually start runlevel changes?  Upstart uses dbus over abstract unix
>> socket (which is containerized with netns), sysvinit uses ioctl over
>> /dev/init which is a distinct file from the one in the container...
>> Does systemd do something we're not containerizing right now?
>>
> fedora 14 uses upstart, not yet systemd which is coming along with
> fedora15
> I have a previously created container with febootstrap of fedora 13 and
> that works, 13 also uses upstart
> so it must be some config
> i tried to diff the packages but couldn't see anything that makes sense
>
>>
>> I'd love to get a working fedora template.
>>
> i'd love to be able to create new fedora containers
>
>>
>> thanks,
>> -serge
>>
>
> classic mistake forgot the attachment
-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20110330/521fb127/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: lxc-fedora.in
Type: application/octet-stream
Size: 10683 bytes
Desc: not available
URL: <http://lists.linuxcontainers.org/pipermail/lxc-users/attachments/20110330/521fb127/attachment.obj>