feat(ansible): re-enable rust_game role on nas - #466
Merged
Conversation
Contributor
There was a problem hiding this comment.
Pull request overview
Re-enables the rust_game Ansible role in the NAS playbook so Rust game server provisioning/management runs again on nas.local, aligning with the stated plan to deploy after the upstream container image is rebuilt with a newer glibc.
Changes:
- Re-enabled the
rust_gamerole inansible/nas.ymlby uncommenting it.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
2 tasks
compscidr
force-pushed
the
jason/enable-rust-game
branch
from
August 3, 2026 01:22
bb1904b to
e7ff81d
Compare
The rust servers were disabled in ae1518c while they were broken. Root cause was the ghcr.io/compscidr/rust-server image being built on ubuntu 20.04 (glibc 2.31) while RustDedicated now requires glibc >= 2.34 — fixed in compscidr/rust-server#1 by moving to the ubuntu 24.04 base. Re-enabling the role so ansible manages the containers again and pulls the fixed image. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
The rust_gameserver container entrypoint chowns /steamcmd to the container user (uid 1000) at startup, but the 'Copy oxide plugins' tasks run after the container is deployed and re-copy oxide.config.json as root:root 644. Oxide then fails to boot with UnauthorizedAccessException when it tries to re-save its config. Copy the files as uid/gid 1000 to match the container user. Co-Authored-By: Claude Fable 5 <noreply@anthropic.com>
compscidr
force-pushed
the
jason/enable-rust-game
branch
from
August 3, 2026 01:59
e7ff81d to
e59ad87
Compare
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Re-enables the
rust_gamerole innas.yml(disabled in ae1518c when the servers broke).Root cause of the breakage:
rust-weekly/rust-monthlywere restart-looping becauseghcr.io/compscidr/rust-serveris built on Ubuntu 20.04 (glibc 2.31) while Facepunch's currentRustDedicatedrequires glibc ≥ 2.34. Fixed in compscidr/rust-server#1 by moving to thenodejs-22-steamcmd-ubuntu-24.04base.Deploy order:
ghcr.io/compscidr/rust-server:latestansible-playbook -i inventory.yml nas.yml --tags rust-weekly,rust-monthly—docker_containerhaspull: true, so it pulls the fixed image and recreates both containers. Saves/config persist in/etc/rust/server/*bind mounts.cs2_gameleft disabled — likely has the same glibc problem, can be tackled separately.🤖 Generated with Claude Code