mirror of
https://github.com/Ayymoss/Plutainer
synced 2026-08-24 14:32:06 -04:00
bbe6e69b6c
One component was blocking an entire architecture. cpp-builder exists only to compile iw4x-launcher and is the sole failing arm64 stage — Wine, plutonium-updater and the T7x path all build fine — yet its failure took Plutonium t4/t5/t6/iw5 and Alterware t7x down with it and left :latest amd64-only. Dockerfile.arm64 now lets that build fail: it records a marker and writes /out/iw4x-launcher.unavailable in place of the binary. Stage 3 copies /out/ as a directory rather than a file, since a file COPY of a missing path would abort the build and reintroduce the coupling; the marker also guarantees the directory is never empty. iw4xentry.sh tests -x on the launcher and, when it is missing, hold_indefinitely's with an explanation naming iw4x/launcher#76 and pointing at the games that do work. Deliberately a capability check rather than an architecture check, so IW4x on arm64 recovers on its own once an image ships a working binary — no code change needed when upstream fixes it. Also: add the iw4x seed to Dockerfile.arm64. It was added to Dockerfile only, so the arm64 image would have shipped without it as soon as arm64 built again — including the sv_maprotation append. Both files now note that the seed blocks are duplicated and must be kept in sync. |
||
|---|---|---|
| .. | ||
| alterentry.sh | ||
| entrypoint.sh | ||
| game-config.sh | ||
| healthcheck.sh | ||
| iw4xentry.sh | ||
| log-watcher.sh | ||
| migrate-v1-to-v2.sh | ||
| plutoentry.sh | ||
| pyquake3.py | ||
| rcon-cli | ||