Looked into your service hermes-agent (69e63935...). The build failure isn't a Hermes problem — your service is configured to build from source (cloning NousResearch/hermes-agent main and running the upstream Dockerfile, which needs apt-get install of build-essential, ffmpeg, Playwright deps, etc).
Two ways forward, and I'd strongly recommend option 1:
Option 1 — Use the prebuilt image (recommended): You already have two other hermes-agent services configured this way (nousresearch/hermes-agent:v2026.4.16 and :latest). For the failing service, change the source from GitHub to prebuilt image and point at nousresearch/hermes-agent:latest. No build step, no apt-get, no network/disk risk — just pull and run.
Option 2 — Keep building from source: Exit code 127 here usually means either the build runner ran out of disk/RAM mid-apt-get, or the image registry hit a transient network blip (the Dockerfile pulls from ghcr.io, docker.io, and archive.ubuntu.com — any one timing out kills the build). Since this is on your own dedicated server (698bfdf929cbe8500af80493), check free disk / memory on the box, then redeploy.
Let me know which way you want to go and I can help walk through the change.
Forum