Here's how I created an LXD/LXC container running OpenWRT:
I used my Ubuntu 16.04 desktop as a host, with lxd installed and configured
(apt-get install lxd; lxd init). You can also use an AWS Ubuntu 16.04 image, or an OpenStack KVM VPS, but you will need some extra networking steps to access the container from outside (e.g. iptables or an HTTP reverse proxy).
Download the latest openwrt rootfs.tar.gz for x86_64 platform
I used: http://downloads.openwrt.org/chaos_calm … tfs.tar.gz
create a metadata.yaml file with the contents:
{
"architecture": "x86_64",
"creation_date": 1472916664,
"properties": {
"architecture": "x86_64",
"description": "openwrt 15.05.1 x86_64 (default) (20160903_18:31)",
"name": "openwrt-15.05.1-x86_64-default-20160903_18:31",
"os": "openwrt",
"release": "15.0.1",
"variant": "default"
}
}Obviously you can update the times. I use a script to generate this file with the current time.
# create a metadata tarball
tar cfz meta.tar.gz metadata.yaml
# import an image with the metadata and rootfs
lxc image import meta.tar.gz openwrt-15.05.1-x86-64-rootfs.tar.gz
# add an alias to the newly created image:
lxc image alias create openwrt <fingerprint> # use the fingerpring printed by the import
# Now create a container. It needs to have privileged permissions:
lxc launch openwrt --config security.privileged=true t1 # "t1" is the name of the container
# Start a shell in the container:
lxc exec t1 ashBusyBox v1.23.2 (2016-01-02 12:56:51 CET) built-in shell (ash)
# ps
1 root 15136 S /sbin/procd
38 root 9296 S ash
48 root 9292 R psNot much is running. It seems to have been partially booted. We'll fix it below, but first, configure the network to use the LXD DHCP server:
edit /etc/config/network and replace the 'lan' interface with:
config interface 'lan'
option ifname 'eth0'
option proto 'dhcp'Now run the following mknod commands. It's a good idea to save them in a script, because you will need to run them every time the container boots:
mknod -m 666 /dev/zero c 1 5
mknod -m 666 /dev/full c 1 7
mknod -m 666 /dev/random c 1 8
mknod -m 666 /dev/urandom c 1I have no idea why this works. I found these lines in lxc/templates/ in the github lxc code.
Running mknod is the reason the container needs privileged permissions.
That's it. The container now runs. You can reboot or halt (which you could not do without the missing devices).
You can find the container's ip address (10.x.x.x) and http to its web interface.
You should also be able to access the internet from the container.
Some things don't work yet:
* rebooting the container loses the devices we created. We need to run mknod again.
I tried putting this in rc.local or /etc/preinit, but it didn't work.
* ssh into the container gives this error:
PTY allocation request failed on channel 0
shell request failed on channel 0
Perhaps someone more knowledgeable can fill-in the missing pieces.
(Last edited by votsalo on 4 Sep 2016, 20:48)