How to Install and Set Up LXD on Ubuntu 16.04

LXD works with a directory based storage backend. LXD is lxc with strong security. We can install LXD, ZFS and Bridge-Utils on Ubuntu 16.04 and configure that LXD to use a physical ZFS partition or loopback device combined with a bridged networking setup allowing for containers to pick up IP addresses via DHCP on the vLAN. For a dedicated server which runs multiple web sites with Linux containers, each web site can be set up in its own container and own web server. Using LXD, we can bundle application and its dependencies in a container without affecting the rest of the system. Here is How to Install and Set Up LXD on Ubuntu 16.04. Official information around LXD can be found on :

 

 

How to Install and Set Up LXD on Ubuntu 16.04

 

LXD normally installed on Ubuntu, but we need to configure and check before we can use it on a going to be production server :

After running the last command, you’ll get an output like below :

Open /etc/network/interfaces :

The file should be configured like this at minimum :

Run :

Run ifconfig command to make sure that the system took the changes. We used a dedicated hard drive for the ZFS storage. For who will use a loopback file, the procedure is somewhat different. We can run :

to check the disk spaces and remove any fstab entry. Open sysctl.conf :

change some config like below :

Open limits.conf file :

change some config like below :

Soft reboot and SSH back on console :

Then run :

It will ask lot of questions, keep everything at default except few. Example :

After completing lxd init step like above, add the br0 interface to the default profile with :

Exactly like Docker, LXD is also image based which provides three main options for obtaining images – remote, built-in, and local imports. In order to see which sources are available, run :

We can use the official Ubuntu image repo to spin up a Ubuntu container with the command :

Or CenOS with this command :

To check the status of the container, run :

You’ll get something like :

To start and stop containers run :