Compare commits

...

22 Commits

Author SHA1 Message Date
1ec22ff3fc docs: add AGENTS.md with dev workflow and YAML conventions 2026-05-19 15:27:21 -04:00
b1dbdb9f2d feat: add Hermes worker anchor and provisioning script for Paperclip employees
- Add x-hermes-worker YAML anchor template in compose.yml
  (CPU-only workers, no GPU passthrough, OpenCode Go provider)
- Add commented worker example with env vars placeholder
- Create scripts/provision-hermes-worker.sh for automated worker
  provisioning (generates port, API key, volume dir, appends service)
- Workers connect to Discord only, isolated per container
- Volumes under /mnt/HoardingCow_docker_data/Hermes/<name>/
2026-05-19 14:13:02 -04:00
29ae32a1c5 Merge pull request 'fix: use ln -sf instead of update-alternatives --set for iptables-nft' (#28) from fix/vpn-iptables-nft-v3 into master
Reviewed-on: #28
2026-05-13 16:59:50 +00:00
8dff094768 fix: use ln -sf instead of update-alternatives --set
update-alternatives --set fails because the base image only registers
iptables-legacy as an alternative. The iptables-nft binary (/usr/sbin/iptables-nft)
exists but isn't in the alternatives database. Direct ln -sf bypasses this.
2026-05-13 12:58:43 -04:00
ec08f5eb5d Merge pull request 'fix: remove apk add iptables-nft — built-in on Alpine 3.18+' (#27) from fix/vpn-iptables-nft-v2 into master
Reviewed-on: #27
2026-05-13 16:49:23 +00:00
611e96b306 fix: remove apk add iptables-nft — built-in on Alpine 3.18+
In Alpine 3.18+, the 'iptables' package IS the nftables variant.
iptables-nft is not a separate package. The binary is already in
the base image — only need to flip update-alternatives.
2026-05-13 12:48:51 -04:00
f184ed957c Merge pull request 'fix: update wg-easy to official ghcr image with iptables-nft' (#26) from fix/vpn-iptables-nft-upstream into master
Reviewed-on: #26
2026-05-13 16:37:35 +00:00
2bf31c7ccc fix: update wg-easy to official ghcr image with iptables-nft
- Switch FROM weejewel/wg-easy:latest (4yr old, Alpine 3.11) to
  ghcr.io/wg-easy/wg-easy:latest (actively maintained, Alpine krypton)
- Use update-alternatives instead of raw ln -sf to flip iptables
  from legacy to nftables backend
- Fix compose build context: ./vpn -> . (Dockerfile was at same level)

The weejewel/wg-easy image lacked iptables-nft package in Alpine 3.11.
The new official image has it available, we just flip the alternatives.
The old ln -sf approach was fragile across Alpine versions.
2026-05-13 12:30:15 -04:00
f44f93e35a Merge pull request 'fix: add Himalaya email CLI to Hermes Docker image' (#25) from fix/himalaya-email-cli into master
Some checks failed
Build Hermes agent / build (push) Has been cancelled
Reviewed-on: #25
2026-05-13 15:03:40 +00:00
4cdd157e3f Merge pull request 'fix: add iptables-nft to wg-easy for nftables-only kernels' (#24) from fix/wg-easy-iptables-nft into master
Reviewed-on: #24
2026-05-13 15:03:25 +00:00
3ba0345887 Merge pull request 'feat: install custom Hermes tools at startup, remove deprecated fix-permissions.sh' (#23) from feat/hermes-custom-tools-startup into master
Some checks failed
Build Hermes agent / build (push) Failing after 2s
Build ollama (gfx906) / build (push) Failing after 2s
Reviewed-on: #23
2026-05-13 13:52:36 +00:00
27571ddb3f feat: add Himalaya email CLI to Hermes Docker image
Some checks failed
Build Hermes agent / build (pull_request) Failing after 2s
2026-05-12 18:09:40 -04:00
5e242eb946 fix: add iptables-nft to wg-easy for nftables-only kernels
wg-easy's Alpine wg-quick uses legacy iptables which requires the
iptable_nat kernel module. On NixOS kernels compiled without legacy
netfilter modules, the container crashes in a restart loop:

  iptables v1.8.3 (legacy): can't initialize iptables table 'nat'
  Table does not exist (do you need to insmod?)

Fix: build a custom image that installs Alpine's iptables-nft package
and symlinks iptables -> iptables-nft (nftables backend).
2026-05-12 14:52:33 -04:00
e607982b21 refactor: chown tools dir at build time instead of root at runtime
Some checks failed
Build Hermes agent / build (pull_request) Failing after 3s
Build ollama (gfx906) / build (pull_request) Failing after 2s
2026-05-12 14:47:34 -04:00
4627199217 feat: install custom tools at startup, remove deprecated fix-permissions.sh
Some checks failed
Build Hermes agent / build (pull_request) Failing after 41m55s
Build ollama (gfx906) / build (pull_request) Failing after 2s
2026-05-12 13:38:26 -04:00
3611d645db Merge pull request 'feat: add Gitea Actions CI workflows for Docker builds' (#21) from feat/gitea-actions into master
Reviewed-on: #21
2026-05-11 02:39:02 +00:00
99ac8b5dcd Merge pull request 'feat: add act_runner and enable Gitea Actions' (#22) from feat/act-runner into master
Reviewed-on: #22
2026-05-11 02:38:41 +00:00
b517a65393 fix: add nixos-builder label for NixOS CI builds 2026-05-10 22:15:44 -04:00
61a59dfac1 Merge pull request 'feat: update Hermes Dockerfile to build from forked source (gortium/hermes-agent)' (#20) from feat/hermes-fork-dockerfile into master
Reviewed-on: #20
2026-05-11 02:07:41 +00:00
144678354f feat: add Gitea Actions runner and enable Actions 2026-05-10 21:38:19 -04:00
34b1cb83a0 feat: add Gitea Actions workflows for ollama and hermes Docker builds 2026-05-10 21:33:10 -04:00
f8c2f864de Merge pull request 'refactor: split ai/ into hermes/ and ollama/ directories with gfx906 build' (#19) from feat/ollama-gfx906 into master
Reviewed-on: #19
2026-05-11 01:26:11 +00:00
11 changed files with 406 additions and 42 deletions

View File

@@ -0,0 +1,31 @@
name: Build Hermes agent
on:
pull_request:
branches: [ master ]
paths:
- 'ai/hermes/**'
- 'ai/compose.yml'
push:
branches: [ master ]
paths:
- 'ai/hermes/**'
- 'ai/compose.yml'
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout
run: |
git clone -b "${{ github.head_ref || github.ref_name }}" \
https://gitea:${{ secrets.GITHUB_TOKEN }}@code.lazyworkhorse.net/gortium/compose.git .
git log --oneline -3
- name: Build hermes image
run: |
cd ai
docker compose build hermes 2>&1
- name: Verify image
run: |
docker run --rm ai-hermes /opt/hermes/.venv/bin/python --version 2>&1

View File

@@ -0,0 +1,31 @@
name: Build ollama (gfx906)
on:
pull_request:
branches: [ master ]
paths:
- 'ai/ollama/**'
- 'ai/compose.yml'
push:
branches: [ master ]
paths:
- 'ai/ollama/**'
- 'ai/compose.yml'
jobs:
build:
runs-on: ubuntu-latest
steps:
- name: Checkout
run: |
git clone -b "${{ github.head_ref || github.ref_name }}" \
https://gitea:${{ secrets.GITHUB_TOKEN }}@code.lazyworkhorse.net/gortium/compose.git .
git log --oneline -3
- name: Build ollama image
run: |
cd ai
docker compose build ollama --no-cache 2>&1
- name: Verify version
run: |
docker run --rm ollama/ollama:rocm-gfx906 ollama --version 2>&1

31
AGENTS.md Normal file
View File

@@ -0,0 +1,31 @@
# AGENTS.md
Development conventions for the compose repository (Docker Compose stacks).
## Build & Deploy
- The ai stack is managed via `systemctl restart ai_stack.service` on the NixOS host
- Compose files are built from the git repo; apply via `nh os switch` or `systemctl restart ai_stack.service`
- Never `docker compose up -d` directly — it bypasses the systemd env file and breaks secrets
## Hermes Workers
- Paperclip Hermes workers are added via `ai/scripts/provision-hermes-worker.sh`
- The script appends only — never deletes or modifies existing content
- Workers are CPU-only containers on the `ai_backend` network with no GPU passthrough
## Workflow
- New feature → clean branch from `origin/master` → push → PR on Gitea
- Branch naming: `feat/description` (features), `fix/description` (bugs/docs)
- Always branch from `origin/master`, never from another feature branch
- Submodule changes (when this repo is consumed as a submodule): commit the submodule update in the parent repo
- PR title should describe the change; body should explain motivation + summary
- After PR merge, delete the feature branch
## YAML Conventions
- Use `x-*` extension fields for reusable anchors
- Comment out inactive services rather than deleting them
- Environment variables in dictionary format (`KEY: value`) for anchor compatibility
- List format (`- KEY=value`) works for standard services but doesn't merge with anchors

View File

@@ -1,4 +1,35 @@
version: "3.8"
# ── Hermes Worker Template ──────────────────────────────────
# Used by paperclip-worker-* Hermes containers via YAML anchor.
# Each worker = one isolated Hermes agent for a Paperclip employee.
# Override at service level: container_name, API_SERVER_PORT,
# API_SERVER_KEY, DISCORD_BOT_TOKEN, volumes.
# Workers have NO GPU — they use OpenCode Go or remote providers.
x-hermes-worker: &hermes-worker
build:
context: ./hermes
ssh:
- default
entrypoint: ["/bin/bash", "-c",
"bash /opt/data/hermes-tools/install.sh && exec /usr/bin/tini -g -- /opt/hermes/docker/entrypoint.sh \"$@\"",
"hermes-entrypoint"]
command: gateway run
restart: always
environment:
API_SERVER_ENABLED: "true"
API_SERVER_HOST: "0.0.0.0"
OLLAMA_HOST: "http://ollama:11434"
OPENROUTER_API_KEY: ${OPENROUTER_API_KEY}
# Each worker needs its own OpenCode Go API key in .env
OPENCODE_GO_API_KEY: ${OPENCODE_GO_API_KEY}
GATEWAY_ALLOW_ALL_USERS: "true"
TZ: "America/Montreal"
networks:
ai_backend:
# NO devices — workers are CPU-only, no GPU passthrough
# ─────────────────────────────────────────────────────────────
services:
# webui:
@@ -31,6 +62,9 @@ services:
ssh:
- default
container_name: hermes
entrypoint: ["/bin/bash", "-c",
"bash /opt/data/hermes-tools/install.sh && exec /usr/bin/tini -g -- /opt/hermes/docker/entrypoint.sh \"$@\"",
"hermes-entrypoint"]
restart: always
# Gateway run enables the internal API server on port 8642
command: gateway run
@@ -93,6 +127,24 @@ services:
- "303"
- "26"
# ── Paperclip Worker Hermes Agents ──────────────────────────
# Each worker is an isolated Hermes agent for a Paperclip employee.
# Add new workers with: ./scripts/provision-hermes-worker.sh <name> <discord-token>
# The API server key and port are generated automatically.
# Workers are CPU-only — they use OpenCode Go or remote providers.
# ── Worker Template (commented — uncomment + configure to activate) ──
# hermes-worker-1:
# <<: *hermes-worker
# container_name: hermes-worker-1
# environment:
# API_SERVER_PORT: "8651"
# API_SERVER_KEY: "generated-by-provision-script"
# DISCORD_BOT_TOKEN: ${WORKER_1_DISCORD_BOT_TOKEN}
# volumes:
# - /mnt/HoardingCow_docker_data/Hermes/worker-1:/opt/data
# ─────────────────────────────────────────────────────────────
networks:
ai_net:
external: true

View File

@@ -61,6 +61,24 @@ urllib.request.urlretrieve(url, base + '/en_US-ryan-high.onnx')
urllib.request.urlretrieve(url + '.json', base + '/en_US-ryan-high.onnx.json')
PYEOF
# ---------- Install Himalaya email CLI ----------
RUN /opt/hermes/.venv/bin/python3 /dev/stdin << 'PYEOF'
import urllib.request, tarfile, os, shutil
url = 'https://github.com/pimalaya/himalaya/releases/download/v1.2.0/himalaya.x86_64-linux.tgz'
tgz = '/tmp/himalaya.tgz'
urllib.request.urlretrieve(url, tgz)
with tarfile.open(tgz) as t:
t.extractall('/tmp')
shutil.move('/tmp/himalaya', '/usr/local/bin/himalaya')
os.chmod('/usr/local/bin/himalaya', 0o755)
os.remove(tgz)
print('himalaya v1.2.0 installed')
PYEOF
# ---------- Install himalaya-ro wrapper ----------
COPY --chmod=0755 himalaya-ro.sh /usr/local/bin/himalaya-ro
# ---------- Runtime ----------
USER hermes
ENV HERMES_HOME=/opt/data
@@ -68,7 +86,8 @@ ENV PATH="/opt/data/.local/bin:${PATH}"
# Point browser tool to Playwright's Chromium (already in base image)
ENV CHROME_EXECUTABLE=/opt/hermes/.playwright/chromium/chrome-linux/chrome
VOLUME [ "/opt/data" ]
# Ensure tools directory and toolsets.py are writable by the hermes runtime user
# so custom tools can be injected from the persistent volume at startup.
RUN chown -R hermes:hermes /opt/hermes/tools /opt/hermes/toolsets.py
COPY --chmod=0755 fix-permissions.sh /opt/hermes/fix-permissions.sh
ENTRYPOINT [ "/usr/bin/tini", "-g", "--", "/opt/hermes/fix-permissions.sh" ]
VOLUME [ "/opt/data" ]

View File

@@ -1,38 +0,0 @@
#!/bin/bash
# Startup permission fix + TTS patch.
# Runs as root before the entrypoint drops to the hermes user.
set -e
HERMES_HOME="${HERMES_HOME:-/opt/data}"
# Fix ownership on critical writable directories
chown -R hermes:hermes \
"$HERMES_HOME/sessions" \
"$HERMES_HOME/checkpoints" \
"$HERMES_HOME/skills" \
"$HERMES_HOME/memories" \
"$HERMES_HOME/workspace" \
"$HERMES_HOME/pastes" \
"$HERMES_HOME/logs" \
"$HERMES_HOME/cron" \
"$HERMES_HOME/plans" \
"$HERMES_HOME/hooks" \
"$HERMES_HOME/cache" \
2>/dev/null || true
# Fix data volume root ownership
if [ "$(stat -c %u "$HERMES_HOME" 2>/dev/null)" != "$(id -u hermes)" ]; then
chown hermes:hermes "$HERMES_HOME" 2>/dev/null || true
fi
# ---------- Patch tts_tool.py: replace Edge TTS with Piper ----------
# Fallback runtime patch in case the volume's site-packages differ from the image.
# Idempotent: if already patched, the script does nothing.
PATCH_SCRIPT="/opt/hermes/patch_tts_tool.py"
if [ -f "$PATCH_SCRIPT" ]; then
echo "Applying TTS patch (Piper only, no Edge fallback)..."
/opt/hermes/.venv/bin/python3 "$PATCH_SCRIPT" 2>&1 || true
fi
# Chain to the official Hermes entrypoint
exec /opt/hermes/docker/entrypoint.sh "$@"

73
ai/hermes/himalaya-ro.sh Normal file
View File

@@ -0,0 +1,73 @@
#!/usr/bin/env bash
# ─────────────────────────────────────────────────────────────
# himalaya-ro — Read-only wrapper for himalaya
#
# Blocks destructive commands and logs audit trail.
# Pass-through for read-only commands (list, read, search).
#
# Usage: himalaya-ro [options] <command> [args...]
#
# Install: place in PATH before the real himalaya, or use
# `ln -sf himalaya-ro /usr/local/bin/himalaya`
# ─────────────────────────────────────────────────────────────
set -o pipefail
# ── Configuration ───────────────────────────────────────────
HIMALAYA_BIN="${HIMALAYA_BIN:-/usr/local/bin/himalaya}"
AUDIT_LOG="${HIMALAYA_AUDIT_LOG:-/var/log/himalaya-audit.log}"
# ── Destructive commands we block ──────────────────────────
BLOCKED_CMDS=(
"message move"
"message delete"
"message copy"
"flag add"
"flag remove"
"folder create"
"folder delete"
"folder rename"
"template send"
"account configure"
"account delete"
)
# ── Determine the subcommand being invoked ─────────────────
# Strip leading options (--account, --output, etc.) to find the verb
ARGS=()
SKIP_NEXT=false
for arg in "$@"; do
if $SKIP_NEXT; then
SKIP_NEXT=false
continue
fi
if [[ "$arg" == --* ]]; then
case "$arg" in
--account|--output|--page|--page-size|--folder|--color|--format)
SKIP_NEXT=true ;;
esac
continue
fi
ARGS+=("$arg")
done
# Build subcommand string and check against blocklist
CMD_STR=""
for ((i=0; i<${#ARGS[@]}; i++)); do
if [ -z "$CMD_STR" ]; then
CMD_STR="${ARGS[$i]}"
else
CMD_STR="$CMD_STR ${ARGS[$i]}"
fi
for blocked in "${BLOCKED_CMDS[@]}"; do
if [[ "$CMD_STR" == "$blocked" ]]; then
TS=$(date '+%Y-%m-%d %H:%M:%S')
echo "[AUDIT] $TS BLOCKED: himalaya $*" >> "$AUDIT_LOG"
echo "ERROR: Command 'himalaya $CMD_STR ...' is blocked by read-only policy." >&2
echo " Audit log: $AUDIT_LOG" >&2
exit 100
fi
done
done
# ── Allow pass-through ─────────────────────────────────────
exec "$HIMALAYA_BIN" "$@"

View File

@@ -0,0 +1,135 @@
#!/usr/bin/env bash
set -euo pipefail
# ── Hermes Worker Provisioner ──────────────────────────────
# Adds a new Paperclip Hermes worker to the ai compose stack.
#
# Usage:
# ./provision-hermes-worker.sh <name> <discord_bot_token_var>
#
# Example:
# ./provision-hermes-worker.sh worker-1 WORKER_1_DISCORD_BOT_TOKEN
#
# The script APPENDS only — never modifies or removes existing
# content, even commented lines.
#
# Post-provision steps (manual):
# 1. Add secrets to agenix .env file
# 2. systemctl restart ai_stack.service
# 3. Configure Paperclip agent
# ─────────────────────────────────────────────────────────────
NAME="${1:?Usage: $0 <name> <discord_bot_token_var>}"
TOKEN_VAR="${2:?Usage: $0 <name> <discord_bot_token_var>}"
# ── Paths ───────────────────────────────────────────────────
SCRIPT_DIR="$(cd "$(dirname "$0")" && pwd)"
COMPOSE_DIR="$(cd "$SCRIPT_DIR/.." && pwd)"
COMPOSE_FILE="${COMPOSE_DIR}/compose.yml"
# Each Hermes worker gets its own volume on the NFS HoardingCow
VOLUME_BASE="/mnt/HoardingCow_docker_data/Hermes"
VOLUME_DIR="${VOLUME_BASE}/${NAME}"
# The Hermes container runs as UID 10000 (hermes user from Dockerfile)
HERMES_UID=10000
# ── Validation ──────────────────────────────────────────────
if ! [ -f "$COMPOSE_FILE" ]; then
echo "❌ compose.yml not found at $COMPOSE_FILE"
exit 1
fi
if grep -q "^ ${NAME}:" "$COMPOSE_FILE"; then
echo "❌ Service '${NAME}' already exists in ${COMPOSE_FILE}"
exit 1
fi
# ── Generate unique API key ─────────────────────────────────
# Used by Paperclip to authenticate against this worker's
# Hermes API server (/v1/chat/completions)
API_KEY="pc_worker_$(openssl rand -hex 16)"
# ── Find next available API port ────────────────────────────
# Workers get sequential ports starting at 8650.
# Scans compose.yml for existing API_SERVER_PORT values and
# picks the next one.
BASE_PORT=8650
MAX_PORT=0
while IFS= read -r line; do
port="${line#*API_SERVER_PORT: \"}"
port="${port%%\"*}"
if [ -n "$port" ] && [ "$port" -gt "$MAX_PORT" ]; then
MAX_PORT="$port"
fi
done < <(grep -oP 'API_SERVER_PORT:\s*"\d+"' "$COMPOSE_FILE" 2>/dev/null)
NEW_PORT=$((MAX_PORT + 1))
if [ "$NEW_PORT" -lt "$BASE_PORT" ]; then
NEW_PORT=$BASE_PORT
fi
# ── Create volume directory (on NFS) ────────────────────────
echo "📁 Creating volume directory: ${VOLUME_DIR}"
mkdir -p "$VOLUME_DIR"
# Hermes container runs as UID 10000 — set ownership so the
# container can write its config, sessions, skills
if command -v chown &>/dev/null; then
chown -R "${HERMES_UID}:${HERMES_UID}" "$VOLUME_DIR" 2>/dev/null || \
echo "⚠ Could not chown ${VOLUME_DIR} — run with sudo if needed"
fi
# Make it group-readable for debugging
chmod 755 "$VOLUME_DIR" 2>/dev/null || true
# ── Append service to compose.yml ───────────────────────────
echo "📝 Appending service '${NAME}' to compose.yml ..."
TMPFILE=$(mktemp)
awk -v name="$NAME" \
-v port="$NEW_PORT" \
-v api_key="$API_KEY" \
-v token_var="$TOKEN_VAR" \
'
# Insert new worker service block just before the networks: section
/^networks:/ {
print ""
print " " name ":"
print " <<: *hermes-worker"
print " container_name: " name
print " environment:"
print " API_SERVER_PORT: \"" port "\""
print " API_SERVER_KEY: \"" api_key "\""
print " DISCORD_BOT_TOKEN: ${" token_var "}"
print " volumes:"
print " - /mnt/HoardingCow_docker_data/Hermes/" name ":/opt/data"
print ""
}
{ print }
' "$COMPOSE_FILE" > "$TMPFILE" && mv "$TMPFILE" "$COMPOSE_FILE"
# ── Done ────────────────────────────────────────────────────
echo ""
echo "✅ Worker '${NAME}' provisioned successfully"
echo ""
echo "────────────────────────────────────────────"
echo " NEXT STEPS"
echo "────────────────────────────────────────────"
echo ""
echo "1. Add secrets to the agenix .env stack file:"
echo ""
echo " # ${NAME}"
echo " ${TOKEN_VAR}=<paste-discord-bot-token-here>"
echo ""
echo "2. Restart the AI stack:"
echo ""
echo " systemctl restart ai_stack.service"
echo ""
echo "3. In Paperclip, create an agent with HTTP adapter:"
echo ""
echo " Endpoint: http://${NAME}:${NEW_PORT}/v1/chat/completions"
echo " API Key: ${API_KEY}"
echo ""
echo "────────────────────────────────────────────"

View File

@@ -7,6 +7,8 @@ services:
- USER_UID=1000
- USER_GID=1000
- GITEA__server__ROOT_URL=https://code.lazyworkhorse.net
- GITEA__actions__ENABLED=true
- GITEA__actions__DEFAULT_ACTIONS_URL=off
- SSH_PORT=2222
- SSH_LISTEN_PORT=2222
# Enable Gitea Actions (act_runner required on host)
@@ -44,6 +46,22 @@ services:
# Internal Routing
- "traefik.http.services.gitea.loadbalancer.server.port=3000"
act_runner:
image: gitea/act_runner:latest
container_name: act_runner
environment:
- GITEA_INSTANCE_URL=https://code.lazyworkhorse.net
- GITEA_RUNNER_REGISTRATION_TOKEN=${GITEA_RUNNER_TOKEN}
- GITEA_RUNNER_NAME=ai-host-runner
- GITEA_RUNNER_LABELS=ubuntu-latest:docker://catthehacker/ubuntu:full-22.04,nixos-builder:docker://nixos/nix
volumes:
- /var/run/docker.sock:/var/run/docker.sock
networks:
- vc_net
restart: always
depends_on:
- gitea
networks:
vc_net:
external: true

9
vpn/Dockerfile Normal file
View File

@@ -0,0 +1,9 @@
# Custom wg-easy with iptables-nft (nftables-backed iptables)
# Fixes crash-loop when host kernel lacks legacy iptable_nat module.
FROM ghcr.io/wg-easy/wg-easy:latest
# The upstream image registers only iptables-legacy with update-alternatives.
# iptables-nft binary exists but isn't registered as an alternative key.
# Override the alternatives-managed symlinks directly.
RUN ln -sf /usr/sbin/iptables-nft /usr/sbin/iptables && \
ln -sf /usr/sbin/ip6tables-nft /usr/sbin/ip6tables

View File

@@ -2,7 +2,10 @@ version: "3.8"
services:
wireguard:
image: weejewel/wg-easy:latest
build:
context: .
dockerfile: Dockerfile
image: wg-easy-iptables-nft:latest
container_name: wireguard
cap_add:
- NET_ADMIN