Add support for running master as a docker container

README.md

@@ -79,6 +79,18 @@ Alternatively, you can download any of the master/node pre-compiled binaries fro
 
 Please refer to [env.md](docs/env.md) to get guidance on how to properly configure master/node usage.
 
+### Docker
+
+The tool was designed to be deployed using the binaries released on GitHub. However, if you want to partially containerize the zero-monitor master agent, you can do it via docker:
+
+```bash
+# First, build the image
+./tools/build-docker
+
+# Finally, start a container
+./tool/run-docker
+```
+
 ## Tech Stack
 
 - Go (echo v4, html/template)

deployments/Dockerfile

@@ -0,0 +1,29 @@
+# This is the base specification for building master agent as a docker image.
+# Use [tools/build-docker] to easily build the image.
+# Use [tools/run-docker] to easily run the container.
+
+FROM golang:1.23.1-alpine AS builder
+WORKDIR /zero-monitor
+
+COPY go.mod ./
+COPY go.sum ./
+
+RUN go mod download
+
+COPY cmd/ ./cmd/
+COPY internal/ ./internal/
+COPY pkg/ ./pkg/
+COPY public/ ./public/
+COPY .version .version
+
+RUN version="$(cat .version)"
+RUN build_pkg="github.com/guackamolly/zero-monitor/internal/build"
+RUN GOOS=linux CGO_ENABLED=0 go build -ldflags="-X $build_pkg.version=$version -X $build_pkg.release=true -extldflags=-static -s -w" -o master ./cmd/master/master.go
+
+FROM scratch
+WORKDIR /zero-monitor
+
+COPY --from=builder /zero-monitor /zero-monitor
+COPY --from=builder /etc/ssl/certs/ca-certificates.crt /etc/ssl/certs/
+
+CMD [ "/zero-monitor/master" ]

tools/build-docker

@@ -0,0 +1,6 @@
+#!/usr/bin/env bash
+
+docker_tag=zero-monitor:latest
+docker build \
+    -f ./deployments/Dockerfile \
+    . -t $docker_tag

tools/run-docker

@@ -0,0 +1,41 @@
+#!/usr/bin/env bash
+
+pwd="$(dirname "$BASH_SOURCE")"
+docker_tag="$(cat $pwd/build-docker | grep "docker_tag=" | cut -d "=" -f 2)"
+
+# Pass -d flag to run container in background as a daemon.
+daemon_flag=""
+if [ "$1" = '-d' ]; then
+    daemon_flag='-d'
+fi
+
+# Ensure volume for app directory exists.
+docker volume create zero-monitor
+
+# If .env is not present, expose bootstrapped ports.
+if [ ! -f .env ]; then
+    docker run $daemon_flag \
+        --mount type=bind,src=/etc/machine-id,dst=/etc/machine-id \
+        -v zero-monitor:/.config/zero-monitor \
+        -p 8080:8080 \
+        -p 36113:36113 \
+        -t $docker_tag
+
+    exit $?
+fi
+
+# (WARNING): Expert docker user only.
+# If .env is present, use values defined there instead of bootstrapped configuration.
+# Paths defined in .env file must be absolute!
+export $(grep -v '^#' .env | xargs)
+docker run $daemon_flag \
+    --mount type=bind,src=/etc/machine-id,dst=/etc/machine-id \
+    --mount type=bind,src=$bolt_db_path,dst=$bolt_db_path \
+    --mount type=bind,src=$mq_transport_pem_key,dst=$mq_transport_pem_key \
+    --mount type=bind,src=$server_tls_crt_fp,dst=$server_tls_crt_fp \
+    --mount type=bind,src=$server_tls_key_fp,dst=$server_tls_key_fp \
+    -v zero-monitor:/.config/zero-monitor \
+    -p $server_port:$server_port \
+    -p $mq_sub_port:$mq_sub_port \
+    --env-file .env \
+    -t $docker_tag