Skip to content

Captain Hook Startup Services

Running Hooks-Subdomains Docker Pod as Startup Service

The webhooks-subdomains docker pod requires two startup services - one keeps the docker pod running, the other watches a folder shared between the host and container for signals from the container, and uses that to trigger updates to the subdomains web content.

Also see the services/ folder of the dotfiles/debian repository, repository for the systemd services.

Service 1: Webhooks Docker Pod

This service keeps the webhooks docker pod service running continuously. If the pod stops, this service will restart it.

(This service should not be running if you are troubleshooting the docker pod.)


Description=webhooks and subdomains docker pod

ExecStart=/usr/local/bin/docker-compose -f /home/charles/codes/docker/pod-webhooks/docker-compose.yml up
ExecStop=/usr/local/bin/docker-compose  -f /home/charles/codes/docker/pod-webhooks/docker-compose.yml down



Description=captain hook canary script

ExecStop=/usr/bin/pgrep -f captain_hook_canary | /usr/bin/xargs /bin/kill 


Now install the service to /etc/systemd/system/dockerpod-webhooks.servce, and/or /etc/systemd/system/captain-hook-canary.servce, and activate it:

sudo systemctl enable dockerpod-webhooks.service

sudo systemctl enable captain-hook-canary.service

Now you can start/stop the service with:

sudo systemctl (start|stop) dockerpod-webhooks.service

sudo systemctl (start|stop) captain-hook-canary.service

As mentioned above, these services should be stopped before doing a docker-compose stop or a docker-compose up --build to keep the pod from respawning in the middle of the task.

Stop using:

sudo systemctl stop dockerpod-webhooks.service

sudo systemctl stop captain-hook-canary.service