Diff for "Running/LXD"

Not logged in - Log In / Register

Differences between revisions 1 and 18 (spanning 17 versions)
Revision 1 as of 2016-05-18 18:37:05
Size: 2378
Editor: bryanquigley
Comment: initial
Revision 18 as of 2022-06-17 12:36:25
Size: 75
Editor: cjwatson
Comment: update link
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 an LXD managed LXC container. [[Running/LXC]] is still the recommended development setup and what most developers currently use.

= Why? =
Launchpad development setup makes significant changes to your machine; it's nice to be unaffected by those when you're not doing such development. Also, multiple containers can be used to work around Launchpad's limitations regarding concurrent test runs on a single machine.

LXD also has some nice snapshoting and ZFS capabilities that I find easier to use with LXD's frontend.

These instructions should work on Ubuntu 14.04 LTS or later. It has only been tested on 16.04 though.

= Create an LXD Container =
This assumes you already have LXD setup. If not, follow the instructions for getting lxd installed and configured on your network: https://linuxcontainers.org/lxd/getting-started-cli/

 1. Create a container
 This command creates a Ubuntu 12.04 32 bit privileged container. Feel free to drop the i386 to use 64 bit if you have the RAM. As of this writing 32 bit takes 700MB and 64 bit takes 1.5GB of memory
 {{{
 lxc launch ubuntu:12.04/i386 lpdev -c security.privileged=true
 }}}
 1. Then share your home directory with the new container. This only works if you make it a privileged container above.
 {{{
 lxc config device add priv homedir disk source=/home/$USER path=/home/ubuntu
 }}}
 1. Find the container IP, either from `lxc list` or `lxc info lpdev`.

 1. Then connect with:
 {{{
ssh -A ubuntu@IP_ADDRESS_FROM_LXC_LS
 
The -A permits you to access Launchpad code hosting from within the container without needing to reenter passphrases.
 }}}
 1. [Inside the container] Install Bazaar so you can run rocketfuel-setup.
 {{{
 sudo apt-get install bzr
 }}}
 1. [Inside the container] You can now follow the normal LP [[Running]] instructions. Be warned that changes in your home directory will also be seen outside the container and vice versa. If your home directory already has a Launchpad work area set up you'll want to run rocketfuel-setup --no-workspace to avoid trying to recreate it, but all subsequent steps are still required.

 1. Follow [[Running/RemoteAccess]] to set up access from the host's applications to the container's Launchpad instance or else going to launchpad.dev won't work.
#refresh 0 https://launchpad.readthedocs.io/en/latest/how-to/running.html

Running/LXD (last edited 2022-06-17 12:36:25 by cjwatson)