Starting docker-compose with systemd on ubuntu 15.04

Question

I have a docker-compose project that I would like to control through systemd. In upstart, I would use a script that looks like this:

description "Start/Stop server"
author "Jim Cortez"

start on filesystem and started docker
stop on runlevel [!2345]

respawn limit 3 240

pre-start script
    # wait (if necessary) for our docker context to be accessible
    while [ ! -f /projects/my_server/docker-compose.yml ]
    do
      sleep 1
    done
    /usr/local/bin/docker-compose -f /projects/my_server/docker-compose.yml up -d
end script

script
    sleepWhileAppIsUp(){
        while docker ps | grep "$1" >/dev/null; do
            sleep 2
        done
    }

    sleepWhileAppIsUp "my_server"
end script

# stop docker container after the stop event has completed
post-stop script
    if docker ps | grep my_server;
    then
        /usr/local/bin/docker-compose -f /projects/my_server/docker-compose.yml stop
    fi
end script

(above adapted from here)

However, I am now running on a docker host that runs Ubuntu 15.04, which has switched to systemd. How can I do the above as a systemd service script? Simply launching the docker-compose daemon will not allow systemd to track and restart in case of failure.

Here is what I have so far:

[Unit]
Description=My Server container
Requires=docker.service
After=docker.service

[Service]
Restart=always
ExecStart=/usr/local/bin/docker-compose -f /projects/my_server/docker-compose.yml up -d
ExecStop=/usr/local/bin/docker-compose -f /projects/my_server/docker-compose.yml stop

[Install]
WantedBy=local.target

Kevin Rood · Answer 1 · 2016-08-09T12:34:19.583

11

I suggest removing the -d option. You do not need to run the containers in the background in this case.

edited Aug 09 '16 at 12:34

answered Jul 19 '16 at 16:50

Kevin Rood

273
3
6

When removing `-d` and executing a start of the unit, it will block the prompt until the container is finished, which, depending on the workload, may be never. – OneK Jan 16 '21 at 15:31

André B. · Answer 2 · 2016-02-22T22:17:07.057

6

I found that: The author uses a similar approach as you http://trackless.ca/2015/12/21/docker-compose-meets-systemd/. But additionally he creates one systemd service for each docker-compose service.

You might consider to convert your docker-compose file to multiple systemd service files to get rid of the docker-compose dependency: http://container-transform.readthedocs.org/ I used that approach, it works fine for simple setups.

edited Feb 22 '16 at 22:17

answered Feb 22 '16 at 12:08

André B.

163
2

1

you might want to put some additional information from the links in your answer, links tend to do not work after some time. – Dennis Nolte Feb 22 '16 at 13:24
1

indeed, the link don't work anymore ^^. – christophe31 Dec 28 '16 at 11:50
Here's an Internet Archive link to the first blog post: http://web.archive.org/web/20161105135126/http://trackless.ca/2015/12/21/docker-compose-meets-systemd/ – pdoherty926 Mar 09 '17 at 00:17

Daniel YC Lin · Answer 3 · 2019-05-02T08:15:26.080

0

Try this, I found in my test, it require more time than normal service to start or stop.

[Unit]
Description=My Server container
Requires=docker.service
After=network.target docker.service

[Service]
#Restart=always
Type=simple
WorkingDirectory=/projects/my_server
ExecStart=/usr/local/bin/docker-compose -f /projects/my_server/docker-compose.yml up
ExecStop=/usr/local/bin/docker-compose -f /projects/my_server/docker-compose.yml down

[Install]
WantedBy=multi-user.target

edited May 02 '19 at 08:15

answered Jul 06 '18 at 01:56

Daniel YC Lin

153
1
2
7

1

i think you should use WorkingDirectory. docker-compose use current working directory to load .env files WorkingDirectory=/projects/my_server also ExecStart=/usr/local/bin/docker-compose up – Mohammadalijf May 01 '19 at 10:49

Starting docker-compose with systemd on ubuntu 15.04

3 Answers3