Helper scripts installed into managed MLXP reservation images at:
~/scripts
The scripts are intended for already-running reservation pods. They do not replace controller-managed registry pull credentials.
snupi-link-persistent-configs: link standard home config paths to existing persistent state under~/worksnupi-docker-login: persist Docker registry auth under~/work/.dockersnupi-git-setup: persist GitHub CLI auth under~/work/.config/ghand global Git config under~/work/.gitconfig
Both helpers prefer DDN-backed ~/work storage so credentials survive pod
recreation. They link the standard home paths back to those persistent
locations, so tools can continue using their defaults. Treat these directories
as sensitive.
If a standard home path already exists and blocks a link, the helper moves it to
a timestamped .snupi-backup-* path before creating the link.
Managed reservation images run snupi-link-persistent-configs during shell
startup after ~/work is available, so credentials set up once are linked again
after a later reservation recreates /root.
Run once inside a managed reservation pod:
snupi-docker-loginThe helper writes Docker auth to:
~/work/.docker/config.json
It also links the default Docker config directory:
~/.docker -> ~/work/.docker
Use this for build and push from inside a reservation. Pulling the reservation
image itself still uses controller-managed registryProfiles.
The default mode uses GitHub CLI with HTTPS Git credentials:
snupi-git-setupThe helper stores GitHub CLI auth under:
~/work/.config/gh
It also stores global Git config under:
~/work/.gitconfig
It links the standard GitHub and Git paths:
~/.config/gh -> ~/work/.config/gh
~/.gitconfig -> ~/work/.gitconfig
For SSH-based Git instead:
snupi-git-setup --protocol sshSSH mode creates a key under ~/work/.ssh and attempts to upload the public key
with gh ssh-key add. If upload fails, the script prints the public key so the
member can add it manually in GitHub.
SSH mode also links:
~/.ssh -> ~/work/.ssh