Repository navigation
fix: use build time ARGs instead of run time ENVs - #191
Conversation
…e values and protect them from manipulation by opinionated container runtimes
|
Fully deleted the setup and started over and the "//" and disk write errors still exist with this release. Vanilla CS2 is fully tested and working. No errors. Only occures on Joedwards32 without the home patch. #!/bin/bash Pelican install prep for CS2 under /home/containerEnforces uid:gid 999:999 and verifies ownership/writeability.set -euo pipefail RUID=999 export LANG=C.UTF-8 ROOT_DIR="/home/container" echo "Using ROOT_DIR=${ROOT_DIR}" Create treemkdir -p Normalize steamapps and compat linkif [ -d "${STEAMAPPDIR}/steamapps" ] && [ ! -L "${STEAMAPPDIR}/steamapps" ]; then Perms and ownership (MANDATORY 999:999)chmod -R u+rwX,g+rwX "${ROOT_DIR}" || { echo "ERROR: chmod ${ROOT_DIR}"; exit 1; } Verify ownership on critical paths (must be 999:999)for p in "${ROOT_DIR}" "${STEAMAPPDIR}" "${INSTALL_DIR}" "${INSTALL_DIR}/game/csgo/cfg" ; do atomic permcheck owned by 999:999install -o ${RUID} -g ${RGID} -m 664 /dev/null "${INSTALL_DIR}/.permcheck" Runtime envexport HOME="${ROOT_DIR}" Summaryecho "Prep complete." |
This is to support alternative container image builds for opinionated runtime environments such as pelican.dev. ref: #190
|
PR updated to parameterize more, allowing for a pelican compatible build like
|
fix: use build time ARGs instead of run time ENVs to declare sensitive values and protect them from manipulation by opinionated container runtimes