Running systemd within a docker container

I have been working on Docker for the last few months, mainly getting SELinux added to help CONTAIN Containers.

libvirt-sandbox – virt-sandbox-service

For the last couple of years I was working on a different container technology using libvirt-lxc, in addition to my regular SELinux job. I built the virt-sandbox-service tool which would carve up your host system into a bunch of service containers.  My idea was to run systemd within a container and then systemd would start services the same way inside a container as it would outside the container.  Running a virt-sandbox-service container with an Apache unit file, you only see systemd, journald and the httpd processes running.  Very little overhead, and creating a service container was simple, you only needed to specify the unit file of the service you wanted to put in the container.

Docker stopped virt-sandbox-service development:

I put virt-sandbox-service on the backburner when it became obvious that the community was moving towards Docker.

While working with Docker, I looked at the great work that Scott Collier was doing for getting services to run within a container.  Scott provides the fedora-dockerfiles package in docker with lots of “Dockerfile” examples. You can build Docker images by running “docker build” on these examples.

It seemed a little difficult, and wondered if getting systemd to run within a docker container, as I did with virt-sandbox-service, might make this simpler.

The Docker Model suggests that it is better to run a single service within a container.  If you wanted to build an application that required an Apache service and a MariaDB database, you should generate two different containers.   Some people insist on running multiple services within a container, and for this Docker suggested using the supervisord tool.  In RHEL we do not want to support supervisord, since it is written in Python, and do not want to pull a Python requirement into containers, and it is just a package used to monitor multiple services.  We already have a tool for monitoring multiple services called systemd.

Can systemd run within a Docker container?

Anyways, I went off to investigate running systemd in a docker container.

First thing I noticed was a few bug reports by others who had failed.

After investigating the failures, I found that systemd requires CAP_SYS_ADMIN capability but Docker drops that capability in the non privileged containers, in order to add more security.  This means for now you have to run systemd within a privileged container since privileged containers do not drop any capabilities.  There is a patch upstream to allow users to add capabilities to a docker container. Once this patch gets merged, I think you would be able to run in a non privileged container by turning on the CAP_SYS_ADMIN capability.

Running a privileged container got me a little further but systemd was still crashing within docker.  Turns out systemd insists on looking at the cgroup file system within a container.  I added the cgroup file system to the container  using the Volume mount

v /sys/fs/cgroup:/sys/fs/cgroup:ro

which allows systemd to look at the cgroup but only in readonly mode.

Systemd ran fully within the container.

But  systemd starts tons of services in the container like udev, getty logins, …  I only want to run systemd, journald, and httpd within the container, I had to stop systemd from starting these other services.

Looking at what I had done to prevent this in virt-sandbox-service, I saw that I needed to remove unit file links from the /lib/systemd/system/*wants/ and  /etc/systemd/system/*wants/ directories within a systemd based docker container.  Removing these links got me to a systemd container image that would only run systemd and journald.


Here is the Dockerfile I wrote to implement a systemd based docker image.

FROM fedora:rawhide
MAINTAINER “Dan Walsh” <>
ENV container docker
RUN yum -y update; yum clean all
RUN yum -y install systemd; yum clean all; \
(cd /lib/systemd/system/; for i in *; do [ $i == systemd-tmpfiles-setup.service ] || rm -f $i; done); \
rm -f /lib/systemd/system/*;\
rm -f /etc/systemd/system/*.wants/*;\
rm -f /lib/systemd/system/*; \
rm -f /lib/systemd/system/*udev*; \
rm -f /lib/systemd/system/*initctl*; \
rm -f /lib/systemd/system/*;\
rm -f /lib/systemd/system/*;
VOLUME [ “/sys/fs/cgroup” ]
CMD [“/usr/sbin/init”]

Notice my DockerFile is using Fedora Rawhide, but this should also work on a RHEL7 or Fedora 20 system.  systemd likes to know that it is running within a container, and it checks the container environment variable for this.  The ENV will cause the “container” environment variable to be set.  Next make sure the image is up to date by running a yum -y update, and cleanup the cache for this image layer.  Next, install the systemd package, and start  removing all of the wants link files.  Finally tell the image it requires the /sys/fs/cgroup volume mounted into it and execute the init command.

I use this command to build the image in the directory containing the Dockerfile

docker build -t systemd_rawhide .

Building an Apache Container Image based on the systemd image.

Now I want to setup a httpd image based on this image, so I create a new Dockerfile.

FROM systemd_rawhide
RUN yum -y install httpd; yum clean all; systemctl enable httpd.service
CMD [“/usr/sbin/init”]

Notice how simple this docker file is to use based on the systemd_rawhide image.  You only have to install the service you want and enable it.  Since this service binds to port 80, you need to specify this in the image.  Finally since systemd will be managing my service within the container you specify /usr/sbin/init as the command to run within the container.

In a different directory, put the new Dockerfile and build the image

docker build -t httpd_rawhide .

Running and testing the Apache Image. 

Now to test the htttpd application container,  start it by executing:

docker run –privileged -ti -v /sys/fs/cgroup:/sys/fs/cgroup:ro -p 80:80 httpd_rawhide

Note that I bind the hosts port 80 to the container port 80.  You can test it by executing:

curl http://localhost

This command should bring you the default Apache page from inside the container.

Running multiple services within a systemd based container image.

If you wanted to run multiple services, you can just install multiple services within the Dockerfile.

RUN yum -y install httpd mariadb ; yum clean all; systemctl enable httpd.service mariadb.service

systemd will start the httpd and mariadb service when you start the container.  Please test and give me feedback on how this works for you.


21 thoughts on “Running systemd within a docker container

  1. Thanks for the details, this sounds promising!

    (for what it’s worth I still really like the idea of libvirt-lxc)

    I tried it out, but systemd still segfaults for me. Peeking in the container, with the `–volume /sys/fs/cgroup:/sys/fs/cgroup:ro` argument I get an empty `/sys/fs/cgroup` directory. If I try mounting it with `–volume /sys/fs/cgroup:/tmp/cgroup:ro` it works fine (I can see my host’s cgroups under /tmp/cgroup), but for some reasn it won’t show up mounted on /sys/fs/cgroup. Perhaps it’s beeing shadowed by /sys/fs or mounted in the wrong order? Relevant `mount` entries are (in this order):

    tmpfs on /sys/fs/cgroup type tmpfs (ro,relatime,mode=755)
    sysfs on /sys type sysfs (rw,nosuid,nodev,noexec,relatime)

  2. Pingback: A Practical Introduction to Docker Containers | Crunch Tools
  3. Thanks for this! I’ve been wanting systemd in my containers for a long time. I will definitely be trying out these steps as soon as I’m back on my computer!

  4. Pingback: A Practical Introduction to Docker Containers | Red Hat Developer Blog
    • Can you tell me what kind of modification you made? Because I still get invalid argument error when I try to run the container. I’m also using Archlinux.

      Error message:
      Error: Cannot start container insane_brattain: Error getting container 79e14aca64332e4bab943a3b12ebd21b730f02a8ab323173f4380e001c5a4e9c from driver devicemapper: Error mounting ‘/dev/mapper/docker-8:1-2367674-79e14aca64332e4bab943a3b12ebd21b730f02a8ab323173f4380e001c5a4e9c’ on ‘/var/lib/docker/devicemapper/mnt/79e14aca64332e4bab943a3b12ebd21b730f02a8ab323173f4380e001c5a4e9c’: invalid argument
      2014/05/22 15:51:22 Error: failed to start one or more containers

      • Pulled the base/arch image for a starting point. Then used this Dockerfile for a ‘systemd_arch’ image:
        FROM base/arch
        MAINTAINER ….
        ENV container docker
        RUN pacman -Syu –noconfirm; \
        (cd /lib/systemd/system/; for i in *; do [ $i == systemd-tmpfiles-setup.service ] || rm -f $i; done); \
        rm -f /lib/systemd/system/*; \
        rm -f /etc/systemd/system/*.wants/*; \
        rm -f /lib/systemd/system/*; \
        rm -f /lib/systemd/system/*udev*; \
        rm -f /lib/systemd/system/*initctl*; \
        rm -f /lib/systemd/system/*;
        VOLUME [ “/sys/fs/cgroup” ]
        CMD [“/usr/bin/init”]

        Next, used this Dockerfile for creating an ‘httpd_arch’ image:
        FROM systemd_arch
        RUN pacman -S apache openssh mc htop –noconfirm; \
        systemctl enable httpd.service; \
        systemctl enable sshd.service
        RUN echo ‘ServerName arch.bogus.domain’ >> /etc/httpd/conf/httpd.conf
        RUN echo ‘root:letmein’|chpasswd
        EXPOSE 80 22
        CMD [“/usr/sbin/init”]

        Here’s my README as a reminder of what I did:
        Build the images:
        1) sudo docker build -t systemd_arch .
        2) sudo docker build -t httpd_arch .
        Run command:
        sudo docker run –privileged -d -v /sys/fs/cgroup -p 8080:80 -p 2222:22 –name=”my_server” httpd_arch

  5. Pingback: Docker, docker everywhere – 42
  6. Hi

    Thanks for some handy baseline for fedora. I was using instead the ssh server.
    Just one thing to add.
    When I started the container I got
    “Failed to mount cgroup at /sys/fs/cgroup/systemd: No such file or directory”

    I have to remove the :ro option from the volume in order to get it around it to continue to start systemd.

  7. I am trying to Dockerize OpenStack services on RHEL7/RDO5. I have started by trying to Dockerize Heat:

    I have almost everything working, except an issue outlined in my latest commit message:

    I can run my script manually in the container and all is good. However, if I run the script in my Docker file I get the following error:

    Error: Could not start Service[heat-api]: Execution of
    ‘/usr/bin/systemctl start openstack-heat-api’ returned 1:
    Failed to get D-Bus connection: No connection to service manager.
    Wrapped exception:
    Execution of ‘/usr/bin/systemctl start openstack-heat-api’
    returned 1: Failed to get D-Bus connection:
    No connection to service manager.

  8. greetings from a total noooob
    shoud not the
    FROM systemd_rawhide
    RUN yum -y install httpd; yum clean all; systemctl enable httpd.service
    EXPOSE 80
    #CMD [“/usr/sbin/init”]
    that is
    this should be removed ? CMD [“/usr/sbin/init”] from httpd_rawhide

      • interesing

        this is a docker image i use to get access to a terminal so i can run systemd commands and write some code to test some ideas

        FROM systemd_rawhide
        RUN yum -y groupinstall “Development Tools”; yum clean all

        then I
        docker build -t=”eduonixdocker/sysd_terminal:1.0.0″ .
        docker run -it –privileged –name sysd_terminal eduonixdocker/sysd_terminal:1.0.0
        docker exec -it sysd_terminal /bin/bash

        then I can
        systemctl list-units -t service –all
        and systemd is availble
        however if I include the

        FROM systemd_rawhide
        RUN yum -y groupinstall “Development Tools”; yum clean all
        CMD [“/usr/sbin/init”]

        systemctl list-units -t service –all fails with messages like no D_Bus ect …

        thanks for this great image systemd_rawhide

Leave a Reply

Fill in your details below or click an icon to log in: Logo

You are commenting using your account. Log Out / Change )

Twitter picture

You are commenting using your Twitter account. Log Out / Change )

Facebook photo

You are commenting using your Facebook account. Log Out / Change )

Google+ photo

You are commenting using your Google+ account. Log Out / Change )

Connecting to %s