Skip to main content

Install and Configure LXC/LXD for Container Management

Hands-On Lab


Photo of Terrence Cox

Terrence Cox

Senior Vice President of Content





Containers are more and more important in any IT environment. Although the most commonly known container management system is Docker, there are other container engines available. In this activity, you will install and configure the Linux Containers (LXC) and learn how to run basic commands to be sure it is available for use.

What are Hands-On Labs?

Hands-On Labs are scenario-based learning environments where learners can practice without consequences. Don't compromise a system or waste money on expensive downloads. Practice real-world skills without the real-world risk, no assembly required.

The development team you are supporting has been working on their web-based API and testing containers. They have completed some testing with Docker, but want to compare their results with a different container engine and management system.

You have been provided access to an Ubuntu 16.04 LTS system with appropriate credentials and permissions. You are being asked simply to install and configure the Linux Containers (LXC) packages for them to begin their testing. When prompted during the configuration utility run, accept the defaults except where indicated in the list below:

  • Provide a subnet value of with a CIDR/Mask value of 24 as the network that containers will reside on the host
  • The first IP served via DHCP to containers should be
  • The last IP served via DHCP to containers should be
  • Provide a maximum of 50 IPs via DHCP for container use from that network
  • Choose NOT to set up an IPv6 connectivity or NAT
  • Name the bridge network device 'lxdbridge0' instead of accepting the default

Be sure you have enable and started the appropriate service(s) and executed the commands to verify the 'cloud_user' account is able to work with the engine itself (add that user to the appropriate group). Once that has been completed, you can turn the system back over to the team for their use.