Linux Container Development
 help / color / mirror / Atom feed
From: "Daniel P. Berrange" <berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
To: "Serge E. Hallyn" <serue-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
Cc: containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org
Subject: Re: An introduction to libvirt's LXC (LinuX Container) support
Date: Wed, 24 Sep 2008 18:27:31 +0100	[thread overview]
Message-ID: <20080924172731.GF30137@redhat.com> (raw)
In-Reply-To: <20080924165307.GA22376-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>

On Wed, Sep 24, 2008 at 11:53:07AM -0500, Serge E. Hallyn wrote:
> Quoting Daniel P. Berrange (berrange-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org):
> > This is a short^H^H^H^H^H long mail to introduce / walk-through some
> >  - Create a simple chroot environment using busybox
> > 
> >     mkdir /root/mycontainer
> >     mkdir /root/mycontainer/bin
> >     mkdir /root/mycontainer/sbin
> >     cp /sbin/busybox /root/mycontainer/sbin
> >     for cmd in sh ls chdir chmod rm cat vi
> >     do
> >       ln -s /root/mycontainer/bin/$cmd ../sbin/busybox
> 
> ITYM ln -s ../sbin/busybox /root/mycontainer/bin/$cmd  ? :)

Yes, clearly :-)

> >  - Create a simple libvirt configuration file for the
> >    container, defining the root filesystem, the network
> >    connection (bridged to br0 in this case), and the
> >    path to the 'init' binary (defaults to /sbin/init if
> >    omitted)
> > 
> >     # cat > mycontainer.xml <<EOF
> >     <domain type='lxc'>
> >       <name>mycontainer</name>
> >       <memory>500000</memory>
> >       <os>
> >         <type>exe</type>
> >         <init>/sbin/init</init>
> >       </os>
> >       <devices>
> >         <filesystem type='mount'>
> >           <source dir='/root/mycontainer'/>
> >           <target dir='/'/>
> >         </filesystem>
> >         <interface type='bridge'>
> >           <source network='br0'/>
> >           <mac address='00:11:22:34:34:34'/>
> >         </interface>
> >         <console type='pty' />
> >       </devices>
> >     </domain>
> >     EOF
> 
> You might want to consider an option to set up mounts
> propagation automatically.  That way the host admin could look under
> /root/mycontainer/proc, /root/mycontainer/sys, etc, and get meaningful
> information.
> 
> >  - Load the configuration into libvirt
> > 
> >     # virsh --connect lxc:/// define mycontainer.xml
> 
> Alas, I'm getting:
> 
>   libvir: Domain Config error : internal error No <source> 'dev' attribute
>   specified with <interface type='bridge'/>
>   error: Failed to define domain from mycontainer.xml
> 
> (libvir is not my typo :)

Several typos :-)

The error message is complaining about the lack of the 'dev' attribute
when it should have been complaining about the the 'bridge' attribute,
and the example I gave is wrong too. In my example XML, change
the interface block to:

         <interface type='bridge'>
           <source bridge='br0'/>
           <mac address='00:11:22:34:34:34'/>
         </interface>


Daniel
-- 
|: Red Hat, Engineering, London   -o-   http://people.redhat.com/berrange/ :|
|: http://libvirt.org  -o-  http://virt-manager.org  -o-  http://ovirt.org :|
|: http://autobuild.org       -o-         http://search.cpan.org/~danberr/ :|
|: GnuPG: 7D3B9505  -o-  F3C9 553F A1DA 4AC2 5648 23C1 B3DF F742 7D3B 9505 :|

      parent reply	other threads:[~2008-09-24 17:27 UTC|newest]

Thread overview: 3+ messages / expand[flat|nested]  mbox.gz  Atom feed  top
2008-09-17 15:06 An introduction to libvirt's LXC (LinuX Container) support Daniel P. Berrange
     [not found] ` <20080917150635.GK27699-H+wXaHxf7aLQT0dZR+AlfA@public.gmane.org>
2008-09-24 16:53   ` Serge E. Hallyn
     [not found]     ` <20080924165307.GA22376-r/Jw6+rmf7HQT0dZR+AlfA@public.gmane.org>
2008-09-24 17:27       ` Daniel P. Berrange [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=20080924172731.GF30137@redhat.com \
    --to=berrange-h+wxahxf7alqt0dzr+alfa@public.gmane.org \
    --cc=containers-cunTk1MwBs9QetFLy7KEm3xJsTq8ys+cHZ5vskTnxNA@public.gmane.org \
    --cc=serue-r/Jw6+rmf7HQT0dZR+AlfA@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