Docker Host

Script and configuration for standing up a Docker host. This includes Docker, multiple configured stacks, and a self-hosted GitHub Actions Runner.

Installation

Right now, installation supports CentOS 7 and Red Hat 9 (which also works with RHEL lookalikes such as Rocky Linux). Actual Docker installation is handled by the installation script, but you can use the stacks installer on any *nix machine, including macOS, by running stacks/setup.sh.

Login as root and execute:

source <(curl -H 'Cache-Control: no-cache, no-store' -o- https://raw.githubusercontent.com/uicpharm/docker-host/main/init.sh)

The script will download the project and walk you through executing the scripts.

If you cannot login as root and can only sudo, then download it to your home directory and execute it from there:

curl -H 'Cache-Control: no-cache, no-store' -o- https://raw.githubusercontent.com/uicpharm/docker-host/main/init.sh > init.sh && \
chmod +x init.sh && \
sudo ./init.sh

FAQs

How do I [insert cool thing here] with the stacks?

For more documentation about the stacks, please view the stacks readme.

Using the deploy script

For all environments, a deploy script is installed in the system that helps with deploying applications that use the docker-host environment. They provide a docker-compose stack and any additional required files (.env file, etc), and then deploy with this script.

It takes these standard steps for deployment of UIC Pharmacy stacks:

• Login to your Docker repo
• Stop the application if it is currently running
• Create a pod (if using podman)
• Start up the stack using the stack path you provide
• Install the stack as a service (if using podman)

Example:

deploy production.yml

This will automatically deploy the application and install it as a service named prior-auth-drug-search-production, if you are running a podman system.

Note if you are using an environment file named something other than .env, you must pass it to the script as well:

deploy production.yml --env-file=production.env

The deploy script can handle upgrades as well. Just pass the --upgrade flag to ensure it handles pulling fresh container images:

deploy production.yml --upgrade

How do I remove the GitHub Runner Service?

If you've installed the GitHub Runner service and now you want to remove it, you can do so by following these steps:

As root:

cd /home/github/runner
./svc.sh stop
./svc.sh uninstall

Then, as the github user:

cd ~/runner
./config.sh remove --token your-token-supplied-by-github