systemd：似乎 ExecStop 脚本在启动命令运行后立即执行

Question

systemd我正在尝试在 RHEL 7 上启动一个 docker-compose 项目作为服务。这是我的systemd脚本 ( /etc/systemd/system/wp.service)：

\n\n

[Unit]\nDescription=wp service with docker compose\nRequires=docker.service\nAfter=docker.service\n\n[Service]\nEnvironmentFile=/home/ec2-user/projects/wp/project-dir/vars.env\nWorkingDirectory=/home/ec2-user/projects/wp/project-dir\n\n# ExecStartPre=/usr/bin/docker-compose down\n\nExecStart=/usr/bin/docker-compose up -d --build --remove-orphans\n\n# ExecStop=/usr/bin/docker-compose down\n\n[Install]\nWantedBy=multi-user.target\n

\n\n

当我执行以下命令时：

\n\n

sudo systemctl status wp.service\n

\n\n

一切正常 - 容器运行并保持运行。这是输出sudo systemctl status wp.service

\n\n

Aug 15 03:07:22 ip-172-31-33-87.ec2.internal docker-compose[4185]: ---> Using cache\nAug 15 03:07:22 ip-172-31-33-87.ec2.internal docker-compose[4185]: ---> 7392974149d3\nAug 15 03:07:22 ip-172-31-33-87.ec2.internal docker-compose[4185]: Successfully built 7392974149d3\nAug 15 03:07:22 ip-172-31-33-87.ec2.internal docker-compose[4185]: Successfully tagged foo_wp:latest\nAug 15 03:07:22 ip-172-31-33-87.ec2.internal docker-compose[4185]: Creating mysql ...\nAug 15 03:07:22 ip-172-31-33-87.ec2.internal docker-compose[4185]: [55B blob data]\nAug 15 03:07:23 ip-172-31-33-87.ec2.internal docker-compose[4185]: [37B blob data]\n

\n\n

并且容器已启动：

\n\n

[ec2-user@ip-172-31-33-87 ~]$ sudo docker container ls -a\nCONTAINER ID        IMAGE                   COMMAND                  CREATED              STATUS                    PORTS                  NAMES\n579b52c8e3bc        foo_wp        "docker-entrypoint.s\xe2\x80\xa6"   About a minute ago   Up About a minute         0.0.0.0:9101->80/tcp   wp\n3c418cfe2b9c        mariadb:10.3.8-bionic   "docker-entrypoint.s\xe2\x80\xa6"   About a minute ago   Up About a minute         3306/tcp               mysql\n

\n\n

但是，如果我取消注释ExecStop上面的行（并运行docker-compos down并重新加载服务），那么容器将在运行后被删除。状态命令的输出为：

\n\n

   Loaded: loaded (/etc/systemd/system/wp.service; disabled; vendor preset: disabled)\n   Active: deactivating (stop) since Wed 2018-08-15 03:12:12 UTC; 7s ago\n  Process: 4862 ExecStart=/usr/bin/docker-compose up -d --build --remove-orphans (code=exited, status=0/SUCCESS)\n Main PID: 4862 (code=exited, status=0/SUCCESS);         : 5165 (docker-compose)\n    Tasks: 2\n   Memory: 19.0M\n   CGroup: /system.slice/wp.service\n           \xe2\x94\x94\xe2\x94\x80control\n             \xe2\x94\x94\xe2\x94\x805165 /usr/bin/python2 /usr/bin/docker-compose down\n\nAug 15 03:12:11 ip-172-31-33-87.ec2.internal docker-compose[4862]: Step 3/3 : COPY wordpress/ /var/www/html/\nAug 15 03:12:11 ip-172-31-33-87.ec2.internal docker-compose[4862]: ---> Using cache\nAug 15 03:12:11 ip-172-31-33-87.ec2.internal docker-compose[4862]: ---> 7392974149d3\nAug 15 03:12:11 ip-172-31-33-87.ec2.internal docker-compose[4862]: Successfully built 7392974149d3\nAug 15 03:12:11 ip-172-31-33-87.ec2.internal docker-compose[4862]: Successfully tagged foo_wp:latest\nAug 15 03:12:11 ip-172-31-33-87.ec2.internal docker-compose[4862]: Creating mysql ...\nAug 15 03:12:11 ip-172-31-33-87.ec2.internal docker-compose[4862]: [55B blob data]\nAug 15 03:12:12 ip-172-31-33-87.ec2.internal docker-compose[4862]: [37B blob data]\nAug 15 03:12:12 ip-172-31-33-87.ec2.internal docker-compose[5165]: Stopping wp    ...\nAug 15 03:12:12 ip-172-31-33-87.ec2.internal docker-compose[5165]: Stopping mysql ...\n

\n\n

并且容器已被移除：

\n\n

sudo docker container ls -a\nCONTAINER ID        IMAGE               COMMAND             CREATED             STATUS              PORTS               NAMES\n[ec2-user@ip-172-31-33-87 foo]$ \n

\n\n

似乎 systemd 服务在脚本ExecStop之后立即执行该脚本ExecStart。可能是什么原因？

\n

Answer 1

您正在分离模式下运行 docker-compose（选项 -d）。启动容器后，docker-compose 将守护容器并退出。

Systemd 监视 docker-compose 的 PID，当它退出时，假设您的程序已停止并将调用命令ExecStop。

尝试在不带 -d 选项的情况下运行它。

systemd 这样做的原因是因为您没有指定单元的类型，并且默认情况下它会恢复为Type=simple.

请参阅Type和ExecStop的官方文档。