// the find
escapingnetwork/core-keeper-dedicated
Dockerfile for automated build of a Core Keeper Dedicated Server
A Docker image for running a Core Keeper dedicated server, handling the SteamCMD installation, ARM64 emulation via Box64, and server lifecycle management through shell scripts. Aimed at players who want to host persistent servers without babysitting a Steam client. Covers both SDR relay and direct-connect network modes.
ARM64 support is genuinely useful — Box64 variants for Raspberry Pi 3/4/5, M1, and Oracle ARM CPUs cover the common self-hosting hardware people actually use. Discord webhook integration with per-event toggles and templated messages is a nice touch that saves you from writing your own log parser. The network mode design is clean: leaving SERVER_PORT empty defaults to SDR with no port-forwarding required, which is the right default for most home setups. Dependabot and a CI workflow that rebuilds the image mean the image doesn't silently rot.
Mod dependencies are manual — the README explicitly warns you have to resolve them yourself, which breaks quickly as soon as you install anything with transitive deps. Shell-based entrypoint across eight scripts is hard to follow and fragile; a logic error in helper-functions.sh or logfile-parser.sh is painful to debug inside a running container. No health check in the Dockerfile means Docker and compose have no way to detect a hung server process — restart policies won't help if the process is alive but stuck. The single `latest` tag with no versioned tags makes rollbacks impossible if an upstream game update breaks the image.