mirror of
https://github.com/Ayymoss/Plutainer
synced 2026-08-24 14:32:06 -04:00
f9a7953652
Some checks failed
Build and Push Docker Image / build (amd64, Dockerfile, false, linux/amd64, ubuntu-latest) (push) Failing after 2s
Build and Push Docker Image / build (arm64, Dockerfile.arm64, true, linux/arm64, ubuntu-24.04-arm) (push) Has been cancelled
Build and Push Docker Image / merge (push) Has been cancelled
* feat: add 7 Days to Die server support
* refactor(scripts): two table-driven families behind one entry script each
Plutainer had five "families" that were really four Call of Duty engines
plus a platform, and a separate entry script per engine. Adding 7 Days to
Die made the mismatch obvious: a SteamCMD game shares nothing with a
Quake-derived one, while a Plutonium T6 and a CoD4x server differ far
less from each other than either does from a Steam install.
There are now two families, and they are platforms:
cod servers Plutainer installs and runs from game files you supply
steam servers SteamCMD installs
Engine (plutonium/iw4x/alterware/cod4x, unity/srcds) drops to a field in
that family's game table, where it belongs. Each family gets one entry
script driven by that table, so the four CoD entry scripts collapse into
games/codentry.sh at 92 lines, and adding a game is a table row rather
than a new script. entrypoint.sh has two branches and gains none per game.
Per-engine behaviour is expressed as hooks resolved most-specific-first:
cod_<hook>_<game> -> cod_<hook>_<base game> -> cod_<hook>_<engine>
so a game inherits its engine and overrides only what genuinely differs.
The same mechanism serves both families, which removed fifteen one-line
pass-through functions on the Steam side.
Hook names are strings, so plutainer_require_hooks verifies the mandatory
ones resolve at startup and prints what it tried. That is not theoretical:
during this refactor a comma-separated suffix list was passed where an
array was wanted, and every server died with no output whatsoever until
plutainer_hook was made to say what it could not find.
The library splits along the same line — core/fs/cod/steam — so a CoD
change never requires reading the Steam helpers. Audited: zero
cross-family calls in either direction. Anything both needed (the symlink
helpers) moved to fs.sh. Renamed from *-config.sh, which was inaccurate
once the files held install logic and launch arguments.
Verified on all ten CoD games (T4/T5/T6 MP+ZM, IW5, IW4x, T7x MP+ZM,
CoD4x): launch commands byte-identical to the originals, correct config
symlinks per engine, health and RCON working.
* feat(protocols): A2S, Source RCON and telnet, split by protocol
pyquake3.py was the only wire protocol Plutainer spoke, which was fine
while every game was Quake-derived. The SteamCMD games are not: 7DTD has
a telnet console and no RCON at all, Source games speak Valve's RCON over
TCP, and none of them answer getstatus.
Protocols now live in scripts/protocols/, split by protocol rather than
by game, because the mapping is many-to-many — Quake3 covers seven CoD
titles, A2S covers four Steam games across three engines, and querying is
a different concern from administering.
healthcheck.sh picks its probe from the family table (STEAM_QUERY) rather
than a hardcoded branch, and keeps the same bar for every game: the server
must name a map it is running. A2S reports one, so "healthy" does not
degrade to "a TCP connect succeeded" for the new family.
rcon-cli keeps its name because that is what people search for, but is now
one small class per protocol behind a dispatch table. It also distinguishes
"this game has no remote console" from "it has one and you have it switched
off", and tells you which setting to change in the second case.
Both try loopback and then the container's own address. Source 1 servers
answer only on the latter: an identical A2S query times out on 127.0.0.1
and replies immediately on the container IP, with the server healthy
throughout. Rather than encode which engines behave which way, try both.
pyquake3.py moves to protocols/quake3.py with its GPL attribution intact.
* fix(logs): let a family opt out of rotation, and skip huge install trees
Rotation is copy-truncate, which is only valid against a writer that
opened its log with O_APPEND — true of every CoD engine, and the reason
the existing implementation is safe. A Unity dedicated server's -logfile
writer keeps its own offset instead, so truncating would leave a sparse
hole and the file's apparent size would snap straight back over the limit,
re-triggering rotation on every poll.
That has not been measured against a running 7DTD, so PLUTAINER_LOG_ROTATE
lets the SteamCMD family turn rotation off. Not rotating is the safe
failure — an unbounded log, which is what the game does unmanaged — rather
than a rotation loop copying gigabytes every two seconds.
PLUTAINER_LOG_PRUNE_DIRS keeps the poller out of a SteamCMD install, which
is tens of thousands of files that would otherwise be walked every two
seconds for one log that does not live there.
* build: add SteamCMD, keep STOPSIGNAL SIGKILL
SteamCMD is fetched but deliberately not bootstrapped at build time.
Running `steamcmd.sh +quit` in the image pulls a few hundred MB of Steam
client into $HOME that every Call of Duty user would then carry forever,
and 340 MB of Xvfb was removed for exactly that reason. It also does not
reliably prevent the first-contact failure it appears to fix, which is
handled with a retry instead.
Placed after everything the CoD families need, so adding or bumping it
never invalidates their layers.
STOPSIGNAL stays SIGKILL. A game with world state to flush cannot be
served by a signal that cannot be trapped, but changing the image default
would alter shutdown for seven servers already running in production to
benefit one new family. Those games ask for SIGTERM per service instead:
stop_signal: SIGTERM
stop_grace_period: 90s
Measured: 7DTD forwards the signal, saves, and exits 0 in 3.5s; the same
image with no stop_signal stops in 254ms as before. The hang case needs no
code — Docker sends SIGKILL itself when the grace period expires.
chmod now covers every *.sh by find rather than a hand-maintained list
that silently rots as scripts move between directories.
* feat(steam): add CS2, L4D2 and Half-Life 2: Deathmatch
Three more games through the SteamCMD family, chosen to stress the table
in different directions rather than to pad the list. Each needed a table
row and, at most, one hook.
HL2:DM is the plain srcds case. L4D2 shares its hooks entirely. CS2 shares
seed, configure, stage and admin with them and overrides only its launch
arguments, because Source 2 has no srcds_run wrapper.
L4D2 needs a two-phase install and it is not optional. Valve restricted
anonymous Linux installation of app 222860: every depot including the
9.5 GB content one is flagged windows, so a plain app_update on Linux
fails with "Invalid platform". This is an open upstream issue
(ValveSoftware/steam-for-linux#11522) that takes LinuxGSM down with it, so
"this used to work" is true and not a local fault. Pulling the content as
Windows and re-running as Linux overlays the native binaries depot on top.
STEAM_INSTALL_PLATFORMS expresses that generically. The result is a genuine
native server — srcds_linux, no Wine, reports "os: Linux Dedicated".
CS2 exposed a real bug in the config handling. link_configs refuses to
replace a real file at the engine path, because for the CoD families that
file is the strongest signal of user intent. Inside a SteamCMD install the
same signal means the opposite: the directory is Steam's, so a real file is
a depot default that the next update restores anyway. CS2 ships a 33-byte
game/csgo/cfg/server.cfg reading "// Defaults in server_default.cfg", so
the fan-out skipped it with a warning and the server ran on stock settings
while app/configs/server.cfg sat there looking correct. Measured before
and after: hostname went from "Counter-Strike 2" to the configured name,
and the name a server browser shows changed with it.
SteamCMD's first contact in a fresh container is also unreliable — it
downloads its own client, re-execs, and an app_update issued before that
settles fails with "Missing configuration". Measured on both 7DTD and
HL2:DM, with the next attempt succeeding, so installs are retried.
Seed configs are hand-written rather than vendored: Valve ships no
server.cfg for any of these. All three ship empty rcon_password and
sv_password, like every other seed here.
* docs: rewrite for two families and eleven games
The docs described five families and a script-per-game layout that no
longer exists, and the 7DTD material from the original PR assumed it was
a one-off rather than the first member of a family.
Reworked around the two-platform model, with per-game specifics where a
reader looks for them: disk footprints (CS2 is 67 GB and will exceed the
health grace period on first start), the GSLT and masterserver-token
equivalence, why clean shutdown is opt-in per service, and what the
depot-config takeover does.
Audited rather than assumed: all fourteen game tags now appear in the
README table, the games reference, the configuration reference and a
working compose example; every environment variable the code reads is in
the reference table; every script is described in CLAUDE.md; no stale
references to the deleted entry scripts remain; all internal doc links
resolve. That audit found two undocumented variables, now added.
* chore: remove the EXAMPLE-docker-compose.yml signpost
The file had already been reduced to a stub pointing at examples/, kept on
the theory that older guides and forum posts link to it. Nothing in the
repo references it any more: every doc that shows a compose file points at
examples/ directly, so the stub was carrying its own rationale and nothing
else.
Also drops the two places that still named it — its .dockerignore entry
(examples/ and *.md already cover everything it excluded) and its
paths-ignore entry in the publish workflow, which was suppressing builds
for a file that no longer exists.
---------
Co-authored-by: Keyboard Sped <93077330+CoreyUK@users.noreply.github.com>
173 lines
7.8 KiB
Text
173 lines
7.8 KiB
Text
# ARM64 variant (Raspberry Pi 5, Ampere, Apple silicon under Linux).
|
|
#
|
|
# Architecture translation strategy:
|
|
# * x86_64 Windows PE (Plutonium/IW4x/T7x .exe) -> Wine 11 thunked WoW64 +
|
|
# libarm64ecfex.dll (FEX as CPU plug-in, shipped by Hangover 11.9).
|
|
# * Linux helper CLIs (plutonium-updater, iw4x-launcher) -> built natively
|
|
# for aarch64 from source. Upstream ships no aarch64-linux release, so the
|
|
# alternative would be running their x86_64 binaries under box64; building
|
|
# native instead drops the user-space x86 emulator from the runtime image.
|
|
#
|
|
# Base: Debian 13 trixie. Hangover publishes official .deb bundles for this
|
|
# exact distro/arch, so Wine 11 is consumed pre-built.
|
|
|
|
# ---------------------------------------------------------------------------
|
|
# Stage 1: build plutonium-updater (Rust) natively for aarch64-linux.
|
|
# ---------------------------------------------------------------------------
|
|
FROM --platform=linux/arm64 rust:1-trixie AS rust-builder
|
|
|
|
RUN apt-get update && apt-get install -y --no-install-recommends \
|
|
git ca-certificates pkg-config libssl-dev \
|
|
&& rm -rf /var/lib/apt/lists/*
|
|
|
|
WORKDIR /build
|
|
RUN git clone --depth 1 https://github.com/mxve/plutonium-updater.rs.git
|
|
WORKDIR /build/plutonium-updater.rs
|
|
RUN cargo build --release
|
|
|
|
# ---------------------------------------------------------------------------
|
|
# Stage 2: build iw4x-launcher (C++ via build2) natively for aarch64-linux.
|
|
# ---------------------------------------------------------------------------
|
|
FROM --platform=linux/arm64 debian:trixie-slim AS cpp-builder
|
|
|
|
ENV DEBIAN_FRONTEND=noninteractive
|
|
|
|
RUN apt-get update && apt-get install -y --no-install-recommends \
|
|
ca-certificates curl wget git \
|
|
g++ gcc make \
|
|
tar xz-utils \
|
|
&& rm -rf /var/lib/apt/lists/*
|
|
|
|
# build2 ships no aarch64-linux binaries; the install script compiles the
|
|
# toolchain from source. The installer uses curl internally to fetch the
|
|
# source tarball (see check_cmd curl in build2-install-*.sh). --trust yes
|
|
# accepts the cppget.org repo cert without manual fingerprint entry
|
|
# (acceptable inside a one-shot build container).
|
|
RUN curl -fL -o build2-install.sh https://download.build2.org/0.18.1/build2-install-0.18.1.sh \
|
|
&& sh build2-install.sh --trust yes --no-check --jobs $(nproc) --yes /usr/local \
|
|
&& rm build2-install.sh
|
|
|
|
WORKDIR /build
|
|
RUN git clone --depth 1 https://github.com/iw4x/launcher.git iw4x-launcher
|
|
WORKDIR /build/iw4x-launcher
|
|
|
|
# bindist-gcc-static.sh prompts for confirmation; -y answers yes. The script
|
|
# emits a flattened .tar.xz under dist-output/ containing only the binary.
|
|
#
|
|
# Best-effort by design. Upstream publishes no aarch64 launcher binary, so this
|
|
# is the only way to get one, and it is periodically broken by upstream changes
|
|
# we cannot pin around from here (currently iw4x/launcher#76: their pregenerated
|
|
# ODB sources are stale relative to their own libodb constraint). Failing the
|
|
# whole arm64 image over it would take Plutonium T4/T5/T6/IW5 and Alterware T7x
|
|
# down with it, none of which need this binary. So record the failure and let
|
|
# iw4xentry.sh refuse only iw4x, at runtime, with an explanation.
|
|
# IW4X_LAUNCHER_REF only exists to key the layer cache on upstream's HEAD. The
|
|
# fetch below still uses #main; without this the RUN's command string never
|
|
# changes, so BuildKit reuses the cached layer and upstream fixes are invisible
|
|
# until the cache is evicted. That matters more now than it looks: the `|| {}`
|
|
# below makes this step exit 0 even when the compile fails, so a *failed*
|
|
# launcher build gets cached as a success and would keep shipping the
|
|
# .unavailable marker long after upstream is fixed. CI passes the resolved
|
|
# commit SHA; the `main` default only affects manual local builds.
|
|
ARG IW4X_LAUNCHER_REF=main
|
|
RUN echo "upstream iw4x/launcher ref: ${IW4X_LAUNCHER_REF}" \
|
|
&& { sh bindist-gcc-static.sh -y -j $(nproc) "launcher@https://github.com/iw4x/launcher.git#main" \
|
|
|| { echo "WARNING: iw4x-launcher failed to build — this image will NOT support PLUTAINER_GAME=iw4x"; \
|
|
touch /build/iw4x-launcher-build-failed; }; }
|
|
|
|
# /out must never be empty: stage 3 copies the directory (not the file) so that
|
|
# a missing binary does not break the COPY, and BuildKit is happier copying a
|
|
# directory that has something in it.
|
|
RUN mkdir -p /out \
|
|
&& if [ -f /build/iw4x-launcher-build-failed ]; then \
|
|
echo "iw4x-launcher could not be built for this architecture. See iw4x/launcher#76." \
|
|
> /out/iw4x-launcher.unavailable; \
|
|
else \
|
|
tar -xJf dist-output/*.tar.xz -C /out \
|
|
&& find /out -type f -name 'launcher' -exec mv {} /out/iw4x-launcher \; ; \
|
|
fi \
|
|
&& ls -la /out
|
|
|
|
# ---------------------------------------------------------------------------
|
|
# Stage 3: runtime image.
|
|
# ---------------------------------------------------------------------------
|
|
FROM --platform=linux/arm64 debian:trixie-slim
|
|
|
|
ENV DEBIAN_FRONTEND=noninteractive
|
|
|
|
RUN apt-get update && apt-get install -y --no-install-recommends \
|
|
ca-certificates \
|
|
wget \
|
|
tar \
|
|
xz-utils \
|
|
unzip \
|
|
jq \
|
|
python3 \
|
|
procps \
|
|
findutils \
|
|
&& rm -rf /var/lib/apt/lists/*
|
|
|
|
# Hangover 11.9 = Wine 11 + FEX + box64 as Wine CPU plug-ins (the in-Wine
|
|
# box64 is unrelated to a Linux-user-space box64; we do not need the latter
|
|
# because the helper CLIs are native aarch64).
|
|
RUN HANGOVER_TAG="hangover-11.9" \
|
|
&& HANGOVER_TAR="hangover_11.9_debian13_trixie_arm64.tar" \
|
|
&& wget -q "https://github.com/AndreRH/hangover/releases/download/${HANGOVER_TAG}/${HANGOVER_TAR}" \
|
|
&& mkdir hangover-pkg \
|
|
&& tar -xf "${HANGOVER_TAR}" -C hangover-pkg \
|
|
&& apt-get update \
|
|
&& apt-get install -y --no-install-recommends ./hangover-pkg/*.deb \
|
|
&& rm -rf hangover-pkg "${HANGOVER_TAR}" /var/lib/apt/lists/*
|
|
|
|
RUN useradd -m plutainer
|
|
|
|
ENV WINEDLLOVERRIDES="mscoree,mshtml="
|
|
|
|
USER plutainer
|
|
WORKDIR /home/plutainer/.plutainer
|
|
|
|
# No X server anywhere in the image: every server we run is headless. t7x needs
|
|
# `-headless` for that (see alterentry.sh); wineboot only warns about the
|
|
# missing display driver and still initialises the prefix.
|
|
RUN wineboot -u && wineserver -w
|
|
|
|
COPY --from=rust-builder --chown=plutainer:plutainer \
|
|
/build/plutonium-updater.rs/target/release/plutonium-updater \
|
|
/home/plutainer/.plutainer/plutonium-updater
|
|
|
|
# Directory copy, not a file copy: when the launcher build failed there is no
|
|
# iw4x-launcher to copy and a file COPY would abort the image build, which is
|
|
# exactly the coupling we are removing. /out then holds the .unavailable
|
|
# marker instead and iw4xentry.sh reports it at startup.
|
|
COPY --from=cpp-builder --chown=plutainer:plutainer \
|
|
/out/ \
|
|
/home/plutainer/.plutainer/
|
|
|
|
# Community config seeds for first-run scaffolding. Entrypoint copies these
|
|
# into the bind mount on start with cp -n (never overwrites user files).
|
|
# Disable per-stack via PLUTAINER_SKIP_SEED.
|
|
#
|
|
# Vendored, not fetched — see the equivalent block in Dockerfile for why, and
|
|
# keep the two in sync. tools/refresh-seeds.sh is the only thing that should
|
|
# rewrite seed-configs/; each game's SOURCE file records its upstream commit.
|
|
COPY --chown=plutainer:plutainer seed-configs/ seed-configs/
|
|
|
|
COPY --chown=plutainer:plutainer scripts/ .
|
|
# Everything executable, rather than a list that silently rots as scripts move
|
|
# between directories.
|
|
RUN find . -type f -name '*.sh' -exec chmod +x {} + && chmod +x rcon-cli
|
|
|
|
USER root
|
|
RUN ln -s /home/plutainer/.plutainer/rcon-cli /usr/local/bin/rcon-cli
|
|
USER plutainer
|
|
|
|
# No SteamCMD here: Valve ships x86_64 binaries only. steamentry.sh finds it
|
|
# missing and refuses with an explanation — a capability check, so the day an
|
|
# arm64 SteamCMD exists, this starts working with no code change.
|
|
|
|
STOPSIGNAL SIGKILL
|
|
|
|
HEALTHCHECK --interval=1m --timeout=10s --start-period=5m --retries=3 \
|
|
CMD ./healthcheck.sh
|
|
|
|
ENTRYPOINT ["./entrypoint.sh"]
|