Jul 172011

I’m using some lxc containers to offer services with less resources than full virtualization (like kvm, virtualbox, etc.) demands for.
At first I was creating the containers I needed basically following Chris Willing’s guide but, being jealous πŸ˜› of the existing templates for the debian based distributions that allow creation of containers with a single command, I tried to assemble one for slackware 13.37, that I personally use at work and at home as a virtualization platform.

The concept is simply reapplying the steps that the slackware setup normally follows but with the necessary changes (mainly omissions) to fit our container environment: so I uncompressed the slackware setup initrd to check Patrick Volkerding’s work

gzip -dc /data/slackware/slackware64-13.37/isolinux/initrd.img | cpio -i -d -H newc --no-absolute-filenames

and had a look at the install shell scripts in /usr/lib/setup.
Then I took as a base the existing lxc-debian template and modified it to:
– download some slackware packages for a minimal installation (many thanks to Vincent Batts for the selection);
– install them in a folder;
– apply all the standard postinstall routines;
– apply the necessary container fixes (many thanks to Chris Willing that pioneered on this and documented it well πŸ™‚ ).

I published the result on github

“…ok, that’s enough!
we want to play with containers too!”

I was getting to it πŸ™‚

If you want to try them you have to decide which kind of networking you want for them: choices are basically between using:
– a network bridge on your network interface, with the containers in the same network segment as the host;
– a network bridge on a dummy interface used as gateway with NAT: the containers will be in a private network segment.

If you want to offer services and you have plenty of ips to use (like in an home network), maybe the first solution can be easier, as you don’t have to use iptables to redirect incoming connections to the private network of the containers.

Slackware-13.37 kernel already supports all you need, so let’s setup our interface, assuming our host eth0 (the primary ethernet interface, in the example) address is and that we are in a class C network with as our gateway.
Here are the step to follow in each situation:

containers on the same network segment as the host

We have to put the interface down because we are going to add it to the bridge, so if you’are doing this through an ssh connection, I suggest you to run this as a script in a screen session, to avoid being cutted off πŸ˜‰

/sbin/ifconfig eth0 down
/sbin/brctl addbr br0
/sbin/brctl setfd br0 0
/sbin/ifconfig br0 netmask promisc up
/sbin/brctl addif br0 eth0
ifconfig eth0 up
route add default gw
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/conf/br0/proxy_arp

At the end the bridge setup should be ok: you can find a version of the script above (to be included in /etc/rc.d/rc.local) here; I also modify /etc/rc.d/rc.inet1.conf on my nodes where I use this configuration to omit eth0 config (the script is enough to bring up the interface on the host running the containers).

Next, we create a configuration file, let’s call it chuckd.config, for the chuckd virtual container that we are going to do: decide a custom hardware address (anything valid should do) and ip (as we said, in the same range)

lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br0
lxc.network.hwaddr = 00:aa:11:bb:22:cc
lxc.network.ipv4 =
lxc.network.name = eth0

containers on a natted private network

In this case the script to bring up the private network is this

/sbin/brctl addbr br0
/sbin/brctl setfd br0 0
/sbin/ifconfig br0 netmask promisc up
echo 1 > /proc/sys/net/ipv4/ip_forward
echo 1 > /proc/sys/net/ipv4/conf/br0/proxy_arp

/usr/sbin/iptables -t nat -A POSTROUTING -o eth0 -j MASQUERADE
# examples of redirections
iptables -t nat -A PREROUTING -p tcp --dport 51 -i eth0 -j DNAT --to
iptables -t nat -A PREROUTING -p tcp --dport 80 -i eth0 -j DNAT --to

at the end of the script you can see some example of redirection of incoming connections toward the containers in the private network.

also the config file changes (with an ip on the same network)

lxc.network.type = veth
lxc.network.flags = up
lxc.network.link = br0
lxc.network.hwaddr = 00:aa:11:bb:22:cc
lxc.network.ipv4 =
lxc.network.name = eth0

– – –

Now we’ll setup our template so we can use it to create the container: change directory to /usr/lib/lxc/templates if you are on a 32 bit system

cd /usr/lib64/lxc/templates
wget --no-check-certificate https://raw.github.com/Ponce/lxc-slackware/master/lxc-slackware
chmod +x lxc-slackware

We are ready to create our first container, chuckd, using lxc-create and a slackware mirror: if not specified, defaults to the main one; here I’m using a local copy

MIRROR= lxc-create -f /path_to/chuckd.config -n chuckd -t slackware

wait some seconds (25, here) and you will have your slackware-13.37 minimal container in /var/lib/lxc/chuckd/rootfs πŸ™‚

But you have to do another step before firing it up, and it’s setting the network parameters in /var/lib/lxc/$container/etc/rc.d/rc.inet1.conf to the one of your network, if you don’t have a dhcp server available


(, and, in the nat example above) and a nameserver in /var/lib/lxc/$container/etc/resolv.conf (here I’m using google’s one)


Then launch a screen session and fire up the container

lxc-start -n chuckd

you’ll see something like this

INIT: version 2.86 booting
INIT: Entering runlevel: 3
Going multiuser...
Updating shared library links:  /sbin/ldconfig &
Starting sysklogd daemons:  /usr/sbin/syslogd /usr/sbin/klogd -c 3 -x
Starting OpenSSH SSH daemon:  /usr/sbin/sshd
Generating public/private rsa1 key pair.
Your identification has been saved in /etc/ssh/ssh_host_key.
Your public key has been saved in /etc/ssh/ssh_host_key.pub.
The key fingerprint is:
27:ac:44:47:c6:9d:a7:c3:e0:1a:5d:44:a5:d7:1e:69 root@chuckd
The key's randomart image is:
+--[RSA1 2048]----+
|       .o+oo.    |
|       oo +... . |
|      .o.+.o. E  |
|     ..oo +. o . |
|      .oS ..  .  |
|     ... o       |
|      .          |
|                 |
|                 |
Generating public/private dsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_dsa_key.
Your public key has been saved in /etc/ssh/ssh_host_dsa_key.pub.
The key fingerprint is:
dd:37:4d:fb:59:0f:06:da:e7:23:0a:55:3b:50:34:d0 root@chuckd
The key's randomart image is:
+--[ DSA 1024]----+
|          .++    |
|           .E.   |
|          . o   .|
|         . * o o.|
|        S + = *.o|
|         .   * o=|
|        .   . o.o|
|         . . . . |
|          .      |
Generating public/private rsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_rsa_key.
Your public key has been saved in /etc/ssh/ssh_host_rsa_key.pub.
The key fingerprint is:
ac:2e:04:67:ba:11:3a:17:fe:6b:4c:80:95:65:26:e9 root@chuckd
The key's randomart image is:
+--[ RSA 2048]----+
|  .++            |
|  ++             |
| +               |
|. E o  .         |
| o O    S        |
|o = o  .         |
| o B  .          |
|  . =.           |
|   ..o.          |
Generating public/private ecdsa key pair.
Your identification has been saved in /etc/ssh/ssh_host_ecdsa_key.
Your public key has been saved in /etc/ssh/ssh_host_ecdsa_key.pub.
The key fingerprint is:
a5:e2:95:07:42:fc:ed:62:e7:c6:29:4a:45:54:17:2d root@chuckd
The key's randomart image is:
+--[ECDSA  256]---+
|     .. ... oo   |
|     ...   .E .  |
|      ..o..  .   |
|       o.=.      |
|      . S..      |
|     . +o.o      |
|      o. = .     |
|     .  . =      |
|      .. o       |

* container chuckd started. *

and the console output will stop there: that means that the container fired up successfully! πŸ™‚
Having it in a screen session means that you can detach the session (ctrl-A D) and reattach when needed (screen -D -r), it’s optional but useful.

After launching, you can connect to its ip via ssh or open a console with

lxc-console -n chuckd

You can install whatever package you use (also full package sets) with slackpkg, but you can alternatively use slapt-get, if you like.

Enjoy virtual containers!

Considerations: lxc aims to process isolation and at the moment it’s not full: the template sets in the default config to start the containers with lxc.cap.drop=sys_admin, but that line can be commented out from the template or per container, if needed.

P.S. if you want to specify your own set of packages for the container, just create a text file with a modified version of this list, following the same syntax

export arch=x86_64
export PACKAGES=" \
a/aaa_base-13.37-$arch-3.txz \
a/aaa_elflibs-13.37-$arch-7.txz \
a/aaa_terminfo-5.8-$arch-1.txz \
a/bash-4.1.010-$arch-1.txz \
a/bin-11.1-$arch-1.txz \
a/bzip2-1.0.6-$arch-1.txz \
a/coreutils-8.11-$arch-1.txz \
n/dhcpcd-5.2.11-$arch-1.txz \
a/dialog-1.1_20100428-$arch-2.txz \
ap/diffutils-3.0-$arch-1.txz \
a/e2fsprogs-1.41.14-$arch-1.txz \
a/elvis-2.2_0-$arch-2.txz \
a/etc-13.013-$arch-1.txz \
a/findutils-4.4.2-$arch-1.txz \
a/gawk-3.1.8-$arch-1.txz \
a/glibc-solibs-2.13-$arch-4.txz \
n/gnupg-1.4.11-$arch-1.txz \
a/grep-2.7-$arch-1.txz \
a/gzip-1.4-$arch-1.tgz \
n/iputils-s20101006-$arch-1.txz \
a/logrotate-3.7.8-$arch-1.txz \
n/net-tools-1.60-$arch-3.txz \
n/network-scripts-13.0-noarch-3.txz \
n/openssh-5.8p1-$arch-1.txz \
a/openssl-solibs-0.9.8r-$arch-3.txz \
a/pkgtools-13.37-noarch-9.tgz \
a/procps-3.2.8-$arch-3.txz \
a/sed-4.2.1-$arch-1.txz \
a/shadow-$arch-2.txz \
a/sharutils-4.11-$arch-1.txz \
ap/slackpkg-2.82.0-noarch-5.tgz \
a/sysklogd-1.5-$arch-1.txz \
a/sysvinit-2.86-$arch-6.txz \
a/sysvinit-functions-8.53-$arch-2.txz \
a/sysvinit-scripts-1.2-noarch-43.txz \
a/tar-1.26-$arch-1.tgz \
a/udev-165-$arch-2.txz \
a/util-linux-2.19-$arch-1.txz \
n/wget-1.12-$arch-1.txz \
a/which-2.20-$arch-1.txz \

then source it before launching lxc-create

. packages_I_need_list

you can also pass to the script a custom SUITE variable to use other versions than 13.37 (but this is untested, as PACKAGES has to be changed too for each SUITE).
P.P.S. 14.9.2011: edited the nat bridge script following Chris Willing’s hints (thanks again! πŸ™‚ ).

Linux Containers (LXC) on SlackwareΒ© 13.37 (Chris Willing)
LXC HOWTO (Dwight Schauer)
lxc-users mailing list
lxc-devel mailing list

Feb 122011

You have a full slackware installed and you want to use it as a LAMP server? here is a basic setup with phpmyadmin, if you like pretty interfaces for database administration (optional), in some easy steps (as root).
This is a superquick guide, for more informations consider reading mRgOBLIN excellent article.

let’s start πŸ™‚

– make executable the init scripts of httpd (apache) and mysql

chmod +x /etc/rc.d/rc.{mysqld,httpd}

– initialize the database and create standard mysql tables (I suggest to read output on screen, it’s interesting)

mysql_install_db --user=mysql

– start the database daemon and execute a post initialization script: you need to input some data for setup (I suggest to accept defaults to questions)

/etc/rc.d/rc.mysqld start

– edit /etc/httpd/httpd.conf: uncomment a line to enable mod_php and add index.php to the DirectoryIndex directive

Include /etc/httpd/mod_php.conf
    DirectoryIndex index.php index.html

– get phpmyadmin from slackbuilds.org, build the package and install it

wget http://slackbuilds.org/slackbuilds/13.37/network/phpmyadmin.tar.gz
tar xf phpmyadmin.tar.gz
cd phpmyadmin
wget $( grep tar.xz phpmyadmin.info | cut -d\" -f2 )
chmod +x phpmyadmin.SlackBuild
PKGTYPE=txz ./phpmyadmin.SlackBuild
installpkg /tmp/phpmyadmin-*.txz

– start the webserver

/etc/rc.d/rc.httpd start

congratulations, your LAMP server is up and running! πŸ˜€
your DocumentRoot is /var/www/htdocs/, put your stuff in there.
you are also free to look around in your phpmyadmin: use the root credentials setted during the mysql_secure_installation step

links http://localhost/phpmyadmin/

if you are on another host you can substitute localhost with the output of this command on the server

/sbin/ifconfig | grep "inet addr" | grep -v "" | cut -d: -f2 | cut -d' ' -f1
Aug 232010

LXDE logo

as I promised, I have added the necessary branches to my slackbuilds.org’s git master fork, so it will be easy to build a complete LXDE desktop using sbopkg.
I used existing slackbuilds.org components, I added alien bob’s scripts adapting them to slackbuilds.org template and I wrote some from scratch.

    UPDATE: all the components are submitted to slackbuilds.org now so there’s no particular need to set up my repository, unless you want latest testing (but working) stuff for current.
    I also removed the gnome-vfs building option because it’s obsolete starting with slackware 13.37; libatasmart, sg3utils, udisk, upower and gvfs are part of slackware since 14.0.
    Other modifications have been done at the end of 2015 following the latest development choices.
    I’ll try to keep it updated with the latest fixes, you can see them in the branch list of the git repository, so you can use them individually.

the quick install guide:

download and install the latest version of sbopkg (if you don’t have it already, as it’s a must-have application for slackware πŸ˜‰ )
Launch it, and only if you using current, go to the Utilities menu and use the Repository option to select the SBo-git repository. If you’re using stable just leave the default settings and jump at the queue part.
You can also use some command line alternatives πŸ˜‰
you can then go back to the main menu and select the Sync option.
If you find any problems syncing (still only in current case), just

rm -fR /var/lib/sbopkg/SBo-git
sbopkg -r

use this text file as /var/lib/sbopkg/queues/lxde.sqf


then launch

sbopkg -i lxde

choose in the dialog to keep the queue options and you’ve only to wait a little. πŸ™‚

at the end, launching xwmconfig you can choose xinitrc.lxde and the next time you enter in X you’ll have a brand new shiny LXDE desktop. πŸ˜€