Diff for "Running/LXC"

Not logged in - Log In / Register

Differences between revisions 1 and 34 (spanning 33 versions)
Revision 1 as of 2010-05-24 23:55:17
Size: 1063
Editor: lifeless
Comment: create
Revision 34 as of 2011-06-23 01:08:13
Size: 4287
Editor: lifeless
Comment: note why we use poweroff
Deletions are marked like this. Additions are marked like this.
Line 1: Line 1:
This page explains how to set up and run Launchpad (for development) inside a VM. ## page was copied from Running/VirtualMachine
This page explains how to set up and run Launchpad (for development) inside a LXC.
Line 5: Line 6:
Launchpad development setup makes numerous changes to your machine; its nice to be unaffected by those except when you are actually doing such development. Launchpad development setup makes significant changes to your machine; its nice to be unaffected by those except when you are actually doing such development.
Line 7: Line 8:
Also, launchpad has limitations on concurrent testing per-machine and so forth - multiple VM's can be used to work around this. Also, launchpad has some limitations on concurrent testing per-machine and so forth - multiple container's can be used to work around this.
Line 10: Line 11:
= Make a VM image = = Make a LXC =
Line 12: Line 13:
 1. Install KVM  1. Install lxc
Line 15: Line 16:
% sudo apt-get install virt-manager sudo apt-get install lxc
Line 18: Line 19:
 1. Download the Lucid server ISO  1. Work around Bug:800456
{{{
sudo apt-get install cgroup-bin
}}}
Line 20: Line 24:
 1. Run virt-manager.  1. Work around Bug:784093
Line 22: Line 26:
 1. Double click on localhost(QEMU) {{{
sudo dd of=/etc/cgconfig.conf << EOF
mount {
 cpu = /sys/fs//cgroup/cpu;
 cpuacct = /sys/fs/cgroup/cpu;
 devices = /sys/fs/cgroup/cpu;
 memory = /sys/fs/cgroup/cpu;
}
EOF
sudo service cgconfig restart
}}}
Line 24: Line 38:
 1. click on the New virtual machine icon  1. Work around Bug:798476 (optional if you run i386 or have a -tonne- of memory and don't care about 64-bit footprint.
    Grab the patch from the bug and apply it to /usr/lib/lxc/templates/lxc-lucid. If you're running i386 already or want a 64-bit lxc then do not pass arch= on the lxc-create command line.
Line 26: Line 41:
 1. follow your nose here, using the ISO as the install media, and allocating no less than 2G of disk and 1G of memory. I suggest 4G if you can spare it.  1. Create a config for your containers
{{{
sudo dd of=/etc/lxc/local.conf << EOF
lxc.network.type=veth
lxc.network.link=virbr0
lxc.network.flags=up
#fuse (workaround for Bug:800886)
lxc.cgroup.devices.allow = c 10:229 rwm
EOF
}}}
Line 28: Line 52:
 1. After its installed, connect to the image and install {{{acpid}}} and {{{openssh-server}}}  1. Create a container
{{{
sudo arch=i386 lxc-create -n lucid-test-lp -t lucid -f /etc/lxc/local.conf
}}}
    If you want to use a proxy
{{{
sudo arch=i386 http_proxy=http://host:port/ lxc-create -n lucid-test-lp -t lucid -f /etc/lxc/local.conf
}}}
    And if you want to set a custom mirror, similar to http_proxy, but set MIRROR= instead.
Line 30: Line 62:
 1. Use ssh-copy-id to copy your public key into the VM.  1. (Outside the container) grab your user id and username so you can setup a bind mount outside the container:
{{{
id -u
id -nu
}}}
Line 32: Line 68:
 1. ssh -A <vm IP address> to connect to the VM. You can now follow the [[Getting|getting-started]] on LP instructions.  1. Start the container
{{{
sudo lxc-start -n lucid-test-lp
}}}
    Ignore the warning about openssh crashing - it restarts on a later event.
    The initial credentials are root:root.

 1. Grab the ip address (handed out via libvirt's dhcp server) - you may wish to ssh in rather than using the console (seems to have better termcap experience).
{{{
ip addr show dev eth0 | grep 'inet'
}}}

 1. The new container won't have your proxy / mirror settings preserved. Customise it at this point before going further if you care about this.

 1. Enable multiverse (rocketfuel-setup wants it, don't ask me why).

 1. Install some additional packages we'll need to run rocketfuel-setup etc.
{{{
apt-add-repository ppa:ubuntu-virt
apt-get update
apt-get install bzr less sudo lxcguest
# select I for 'install' when prompted about console.conf
}}}

 1. Inside the container add the user:
{{{
adduser --uid $id $username
adduser $username sudo
}}}

 1. To stop it now run 'poweroff -n' (normally you would use lxc-stop, but see Bug:784093).

 1. Setup a bind mount so you can access your home dir (and thus your LP source code) from within the lxc container:
    * edit /var/lib/lxc/lucid-test-lp/fstab
    * Add a line:
{{{
/home/$username /var/lib/lxc/lucid-test-lp/rootfs/home/$username none bind 0 0
}}}
 
 1. Start it up again - headless now, we have the ip address from before.
{{{
sudo lxc-start -n lucid-test-lp -d
# if you created a 32 bit lxc on a 64 bit host you need to mask
# the architecture: (this will also be covered when lxc supports
# this directly - e.g. in oneiric
sudo lxc-start -n lucid-test-lp -d usr/bin/linux32 sbin/init
}}}

 1. ssh <vm IP address> to connect to the VM. Your ssh key is already present because of the bind mount to your home dir.

 1. You can now follow the [[Getting|getting-started]] on LP instructions. Be warned that changes in ~ will affect you outside the container. You will want to run rocketfuel-setup with --no-workspace if your home already has a workarea.

 1. You probably want to follow [[Running/RemoteAccess]] has a discussion for how you can configure things so your non-container browser can access web pages from within the container.

= References =


= Alternatively =

You can also run in a [[Running/Schroot|chroot]] environment or a [[Running/VirtualMachine|VM]].

This page explains how to set up and run Launchpad (for development) inside a LXC.

Why?

Launchpad development setup makes significant changes to your machine; its nice to be unaffected by those except when you are actually doing such development.

Also, launchpad has some limitations on concurrent testing per-machine and so forth - multiple container's can be used to work around this.

Make a LXC

  1. Install lxc

sudo apt-get install lxc
  1. Work around 800456

sudo apt-get install cgroup-bin
  1. Work around 784093

sudo dd of=/etc/cgconfig.conf << EOF
mount {
 cpu = /sys/fs//cgroup/cpu;
 cpuacct = /sys/fs/cgroup/cpu;
 devices = /sys/fs/cgroup/cpu;
 memory = /sys/fs/cgroup/cpu;
}
EOF
sudo service cgconfig restart
  1. Work around 798476 (optional if you run i386 or have a -tonne- of memory and don't care about 64-bit footprint.

    • Grab the patch from the bug and apply it to /usr/lib/lxc/templates/lxc-lucid. If you're running i386 already or want a 64-bit lxc then do not pass arch= on the lxc-create command line.
  2. Create a config for your containers

sudo dd of=/etc/lxc/local.conf << EOF
lxc.network.type=veth
lxc.network.link=virbr0
lxc.network.flags=up
#fuse (workaround for Bug:800886)
lxc.cgroup.devices.allow = c 10:229 rwm
EOF
  1. Create a container

sudo arch=i386 lxc-create -n lucid-test-lp -t lucid -f /etc/lxc/local.conf
  • If you want to use a proxy

sudo arch=i386 http_proxy=http://host:port/ lxc-create -n lucid-test-lp -t lucid -f /etc/lxc/local.conf
  • And if you want to set a custom mirror, similar to http_proxy, but set MIRROR= instead.
  1. (Outside the container) grab your user id and username so you can setup a bind mount outside the container:

id -u
id -nu
  1. Start the container

sudo lxc-start -n lucid-test-lp
  • Ignore the warning about openssh crashing - it restarts on a later event. The initial credentials are root:root.
  1. Grab the ip address (handed out via libvirt's dhcp server) - you may wish to ssh in rather than using the console (seems to have better termcap experience).

ip addr show dev eth0 | grep 'inet'
  1. The new container won't have your proxy / mirror settings preserved. Customise it at this point before going further if you care about this.
  2. Enable multiverse (rocketfuel-setup wants it, don't ask me why).
  3. Install some additional packages we'll need to run rocketfuel-setup etc.

apt-add-repository ppa:ubuntu-virt
apt-get update
apt-get install bzr less sudo lxcguest
# select I for 'install' when prompted about console.conf
  1. Inside the container add the user:

adduser --uid $id $username
adduser $username sudo
  1. To stop it now run 'poweroff -n' (normally you would use lxc-stop, but see 784093).

  2. Setup a bind mount so you can access your home dir (and thus your LP source code) from within the lxc container:
    • edit /var/lib/lxc/lucid-test-lp/fstab
    • Add a line:

/home/$username /var/lib/lxc/lucid-test-lp/rootfs/home/$username none bind 0 0
  1. Start it up again - headless now, we have the ip address from before.

sudo lxc-start -n lucid-test-lp -d
# if you created a 32 bit lxc on a 64 bit host you need to mask 
# the architecture: (this will also be covered when lxc supports 
# this directly - e.g. in oneiric
sudo lxc-start -n lucid-test-lp -d usr/bin/linux32 sbin/init
  1. ssh <vm IP address> to connect to the VM. Your ssh key is already present because of the bind mount to your home dir.

  2. You can now follow the getting-started on LP instructions. Be warned that changes in ~ will affect you outside the container. You will want to run rocketfuel-setup with --no-workspace if your home already has a workarea.

  3. You probably want to follow Running/RemoteAccess has a discussion for how you can configure things so your non-container browser can access web pages from within the container.

References

Alternatively

You can also run in a chroot environment or a VM.