Compiling and running VPP in LXD container revisited

<h1>Compiling and running VPP in LXD container revisited</h1>

<p>
A while ago I wrote about <a href="http://stdio.be/blog/2016-04-01-First-shot-at-running-VPP-inside-LXD-container/">Compiling and running VPP inside LXD container</a>.
</p>

<p>
Since then this has become my primary workflow - one LXD container per
work task, pleasant, modular, reproducible and easy to clean.
</p>

<p>Needless to say, manually going through all the steps is quite boring.
So I wrote a couple of scripts automating the creation of the logistics -
so I can issue a command and attend to other things, and a few minutes
later I have the container with all the dependencies installed,
VPP tree checked out and all the things done up to and including "make build".
This is quite handy for me, so I thought to document this for anyone 
interested.
</p>

<p>First, create a directory called "shared" in your home directory.
This is not VPP-specific, just very very handy for exchanging the data, and
as a default persistent data store that survives the container being deleted.
</p>

<p> Then ensure your LXD profiles are set up right. Run 
"lxc profile create hugepages", "lxc profile create tuntap" 
and then "lxc profile edit hugepages" and "lxc profile edit tuntap" 
and "lxc profile edit default", to edit the profiles so that
you get the results of "lxc profile show ..." identical to below:
</p>

<pre><b>
ayourtch@xenial:~$ lxc profile show hugepages
name: hugepages
config:
  raw.lxc: |
    lxc.mount.entry = hugetlbfs dev/hugepages hugetlbfs rw,relatime,create=dir 0 0
  security.privileged: "true"
description: ""
devices: {}


ayourtch@xenial:~$ lxc profile show tuntap
name: tuntap
config: {}
description: ""
devices:
  tun:
    path: /dev/net/tun
    type: unix-char


ayourtch@xenial:~$ lxc profile show default
name: default
config: {}
description: Default LXD profile
devices:
  eth0:
    name: eth0
    nictype: bridged
    parent: lxdbr0
    type: nic
  shared:
    path: /shared
    source: /home/ayourtch/shared
    type: disk
ayourtch@xenial:~$
</b></pre>


<p><b><font color="red">NOTE:</font></b> You still MUST ensure hugepages are enabled on the host, i.e. this step from the previous blog post is done:</p>

<pre><b>
ayourtch@xenial:~$ echo "vm.nr_hugepages=1024" | sudo tee -a /etc/sysctl.d/20-hugepages.conf
vm.nr_hugepages=1024
ayourtch@xenial:~$
ayourtch@xenial:~$ sudo sysctl --system
ayourtch@xenial:~$ sudo sysctl vm.nr_hugepages
vm.nr_hugepages = 1024
ayourtch@xenial:~$
</b></pre>


<p>
Then, copy the "<b>vpp-bootstrap</b>" file,
which you can find at this blogpost below, into
<b>~/shared/vpp-bootstrap</b>. You can call this file yourself from a newly
created container, or use the "<b>16-vpp-new-dev</b>" script to create and adjust the container for you.</p>

<p>
You will also notice that the scripts try to copy the files from <b>/shared/dot-ssh/*</b> into the new container - I use this to avoid having to re-add the ssh keys ont the server side each time I create the container. Since the containers
stay on the same host, are the same user, I think it is a reasonable approach.
</p>

<p>
Contact me on twitter <a href="https://twitter.com/ayourtch">@ayourtch</a> or via email with any feedback!
</p>