lrz-docker-enroot-refresh

Deploying Docker images as Enroot containers on the LRZ cluster requires building the image locally, pushing it to a registry, importing it via SSH, and safely swapping the active image. This Skill automates that entire lifecycle for robot learning workflows.

Automating container image swaps on Slurm without interrupting jobs is achieved through a safe swapping mechanism that builds and pushes the new Docker image, imports it as an Enroot image, and replaces the active image. This minimizes downtime and risk.

Yes, you can manage distinct robot learning stages using profile-based workflows that support stage-1/2 for foundation models and stage-3 for policy deployment. The Skill handles specific container requirements for each stage profile.

Yes, you need Docker, SSH, and Slurm job submission capabilities to build and push LRZ Enroot images. These dependencies are required for local image construction, remote cluster communication, and executing the deployment.

Enroot image deployment failures during Slurm job submission often stem from missing prerequisites or environment misconfigurations. This Skill implements robust error handling and backup mechanisms to manage these risks during the image swap.

Yes, the lrz-docker-enroot-refresh skill supports automated backup and error handling for cluster deployments. It ensures safe deployment by managing the Docker image lifecycle and implementing backup mechanisms during the Enroot image swap.