Enjoy Slackware 15.0!

Welcome to the Slackware Documentation Project

Trace:

Differences

This shows you the differences between two versions of the page.

Link to this comparison view

Both sides previous revision Previous revision
Next revision 		Previous revision
Next revision Both sides next revision
howtos:misc:lxc [2018/09/14 05:11 (UTC)]
montagdude 		howtos:misc:lxc [2018/10/19 22:00 (UTC)]
mralk3
Line 4: Line 4:
 ===== Introduction ===== ===== Introduction =====
  
-Linux Containers, or LXC, is operating system-level method for running multiple separate isolated Linux installations (containers) on a single host. Rather than simulating the computer hardware as in true virtualization, LXC uses the cgroups and namespaces functionality of the host's Linux kernel to provide strong isolation of the container. It is an intermediate solution between chroots and full virtualization, having a small impact on system resource usage similar to chroots, but providing better isolation. They provide a very convenient way to, among other things, maintain a clean build environment or test software against different [Linux] OS versions.+Linux Containers, or LXC, is operating system-level method for running multiple separate isolated Linux installations (containers) on a single host. Rather than simulating the computer hardware as in true virtualization, LXC uses the cgroups and namespaces functionalities of the host's Linux kernel to provide strong isolation of the container. It is an intermediate solution between chroots and full virtualization, having a small impact on system resource usage similar to chroots, but providing better isolation. It provides a very convenient way to, among other things, maintain a clean build environment or test software against different [Linux] OS versions.
  
 ===== Setting up a Network Bridge ===== ===== Setting up a Network Bridge =====
Line 36: Line 36:
 </code> </code>
  
-The name of the bridge, gateway, netmask, and many other parameters can be modified in /etc/default/lxc/lxc-net. For a complete list, simply open up /usr/libexec/lxc/lxc-net in your favorite editor or pager; there is a comment indicating which variables can be changed.+The name of the bridge, gateway, netmask, and many other parameters can be modified by setting the proper variables in /etc/default/lxc/lxc-net. For a complete list, simply open up /usr/libexec/lxc/lxc-net in your favorite editor or pager; there is a comment indicating which variables can be changed. Set them in /etc/default/lxc/lxc-net rather than modifying /usr/libexec/lxc/lxc-net directly.
  
 To actually use this network within the container, there are a few steps that will need to be taken during the initial creation and setup of the container, which will be covered in the next section. To actually use this network within the container, there are a few steps that will need to be taken during the initial creation and setup of the container, which will be covered in the next section.
Line 76: Line 76:
 </code> </code>
  
-When lxc-create is created, the container will be created at lxcpath/container_name, and slackpkg will download and install the packages needed for a minimal install. The mirror will also be appended to /etc/slackpkg/mirrors.+When lxc-create is executed, the container will be created at $lxcpath/container_name, and slackpkg will download and install the packages needed for a minimal install. The mirror will also be appended to /etc/slackpkg/mirrors.
  
 ===== Container Configuration ===== ===== Container Configuration =====
  
-==== Logging In ====+After creating the container, you are almost ready to go. First start the container: 
 + 
 +<code> 
 +lxc-start -n container_name 
 +</code> 
 + 
 +To log in, use: 
 + 
 +<code> 
 +lxc-console -n container_name 
 +</code> 
 + 
 +or  
 + 
 +<code> 
 +lxc-attach -n container_name 
 +</code> 
 + 
 +The first variant will give you a login console on the container, whereas the second will just give you a root shell without asking for a password. The first thing to do is to create a new user; use the standard Slackware tools such as //adduser//. It makes sense to create a user with the same username as a regular user on the host, because it makes ownership of shared directories easier to manage (more on that later).
  
 ==== Network ==== ==== Network ====
 +
 +Even if you successfully set up a bridge network on the host and configured your container to use a virtual ethernet interface as described above, at this point you will probably still not have network access in the container. The reason is that you still need to set up your container's startup scripts to use the network. If you use lxc-net to set up the bridge network on the host, then you can just have your container get an IP address via DHCP. Open /etc/rc.d/rc.inet1.conf and set this:
 +
 +<code>
 +USE_DHCP[0]="yes"
 +</code>
 +
 +If desired, it should be possible to use a static IP address in the container as well.
 +
 +<note tip>
 +The minimal Slackware installation set up by lxc-create does not have a lot of choice in editors, but //vi// (symlink to //elvis//) is available. If that's not your cup of tea, you can always edit the container's config files from the host using whichever editor you prefer. The container's entire filesystem is at $lxcpath/container_name/rootfs.
 +</note>
 +
 +Once you have edited /etc/rc.d/rc.inet1.conf, get out of the container using Ctrl+a then q. Stop the container and then restart it as follows:
 +
 +<code>
 +lxc-stop -n container_name
 +lxc-start -n container_name
 +</code>
 +
 +Wait a minute or so to give the container plenty of time to "boot" and connect to the network. Then, you can use lxc-ls to check on the status of the container, as follows:
 +
 +<code>
 +# lxc-ls --fancy
 +NAME                STATE   AUTOSTART GROUPS IPV4      IPV6 
 +Slackware-14.2      STOPPED 0         -      -         -    
 +Slackware64-14.2    RUNNING 0         -      10.0.3.65 -    
 +Slackware64-current STOPPED 0         -      -         -
 +</code>
 +
 +If the container successfully connected to the network, you should see that an IP address has been assigned. Log into the container again, and you should be able to ping outside, use slackpkg, etc. At this point, you can install any additional software you desire on the container. If you are using the container as a build environment, for example, you can do a full install:
 +
 +<code>
 +slackpkg install slackware
 +</code>
 +
 +or
 +
 +<code>
 +slackpkg install slackware64
 +</code>
 +
 +==== Custom Container Boot Process ====
 +
 +In order to customize the boot process you can add or modify the init scripts listed in **/usr/share/lxc/scripts/slackware**.  Any changes you make to the existing scripts will be copied to **/etc/rc.d/** in each freshly created LXC container.  This will allow you to easily customize the boot process if you create many LXC containers.  A good example is if you add a custom rc.inet1.conf.  It can become a bit tedious if you wish to create several LXC containers that all use DHCP network addressing.  The solution is to create your own rc.inet1.conf, set **USE_DHCP[0]="yes"**, named it **rc.inet1.conf.lxc**, and save it in **/usr/share/lxc/scripts/slackware**.  Your custom rc.inet1.conf will be copied to each new container.
  
 ==== Sharing Directories with the Host ==== ==== Sharing Directories with the Host ====
  
-===== Checking Container Status =====+Because an LXC container's filesystem is just a directory on the host, if you only need to transfer files from the host to the container, you can simply copy them over. However, often you will want to share the files both ways, or rather, be able to access //the same files// within the container without having to actually transfer anything, and this is a little more difficult due to the isolation of the container. LXC provides utilities to mount host directories on containers for this purpose. We will assume that the directory to be shared is at /home/username/foo on the host. To share a user directory with the host, first log into the container and create the top-level of the directory to be shared. Then log out and stop the container. Add the following lines to the container's config file ($lxcpath/container_name/config): 
 + 
 +<code> 
 +lxc.mount.entry = /home/username/foo home/container_user/foo none bind 0 0 
 +</code> 
 + 
 +Note that the second path intentionally lacks a leading slash. This is because it is a relative path -- relative to the container's rootfs. Once you start the container again and log in, you should see that the directory has been mounted at /home/container_user/foo. In general, it is best if the username on the host is the same as the container's username, because it avoids any conflicts in file ownership between the host and container user. 
 + 
 +====== See Also ====== 
 + 
 +[[https://en.wikipedia.org/wiki/LXC|Wikipedia]] 
 + 
 +[[https://linuxcontainers.org/|LXC homepage]] 
 + 
 +[[https://wiki.debian.org/LXC|Debian wiki]] 
 + 
 +[[https://www.linuxquestions.org/questions/slackware-14/starting-lxc-container-in-slackware-14-2-a-4175614421/|LQ thread]]
  
 ====== Sources ====== ====== Sources ======
Line 92: Line 171:
 <!-- * Original source: [[http://some.website.org/some/page.html]] --> <!-- * Original source: [[http://some.website.org/some/page.html]] -->
 <!-- Authors are allowed to give credit to themselves! --> <!-- Authors are allowed to give credit to themselves! -->
-<!-- * Originally written by [[wiki:user:xxx | User X]] -->+* Originally written by [[wiki:user:montagdude | montagdude]]
 <!-- * Contributions by [[wiki:user:yyy | User Y]] --> <!-- * Contributions by [[wiki:user:yyy | User Y]] -->
  

In Other Languages
QR Code
QR Code howtos:misc:lxc (generated for current page)