In Fedora 17 there are still a number of services that either have not been ported over to systemd or that do not take full advantage of systemd. I've been investigating some IP failover solutions recently, including ucarp, which includes only a System-V style init script.

I've created a template …

I've been working with Arch Linux recently, which uses dhcpcd as its default DHCP agent. If you try booting Arch inside an LXC container, you will find that dhcpcd is unable to configure your network interfaces. Running it by hand you will first see the following error:

# dhcpcd eth0
dhcpcd …

It took me an unreasonably long time to boot an LXC container with working console access. For the record:

When you boot an LXC container, the console appears to be attached to a pts device. For example, when booting with the console attached to your current terminal:

# lxc-start -n node0 …

I spent some time today looking at systemd (44) under Fedora (17). When stopping an LXC container using lxc-stop, I would always encounter this problem:

# lxc-stop -n node0
lxc-start: Device or resource busy - failed to remove cgroup '/sys/fs/cgroup/systemd/node0

This prevents one from starting a new container …

I was intrigued by this post on socket activated containers with systemd. The basic premise is:

• systemd opens a socket on the host and listens for connections.
• When a client connections, systemd spawns a new container.
• The host systemd passes the connected socket to the container systemd.
• Services in the …