-
Notifications
You must be signed in to change notification settings - Fork 7
Commit
This commit does not belong to any branch on this repository, and may belong to a fork outside of the repository.
- Loading branch information
Showing
1 changed file
with
4 additions
and
4 deletions.
There are no files selected for viewing
This file contains 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
Original file line number | Diff line number | Diff line change |
---|---|---|
@@ -1,15 +1,15 @@ | ||
--- | ||
title: "Installing a container engine" | ||
teaching: 10 | ||
exercises: 10 | ||
exercises: 0 | ||
questions: | ||
- What does the procedure to install a container engine looks like, and what are its main caveats? | ||
- What are the key aspects that can be configured by system administrators for Singularity and Shifter deployments? | ||
- What are the key aspects that can be configured by system administrators for container engine deployments? | ||
objectives: | ||
- Familiarise with the high-level procedure to install container runtimes | ||
- Familiarise with the syntax of configuration files for Singularity and Shifter | ||
- Familiarise with the syntax of configuration files for Singularity and other runtimes | ||
keypoints: | ||
- Installation of Singularity and Shifter is relatively simple, however it requires administrative privileges | ||
- Installation of some runtimes is relatively simple, however some require administrative privileges or certain features to be enabled | ||
- Charliecloud can be installed by unprivileged users | ||
- Typical configurations include runtime authorisations, image registry locations, default host directory mounts, default environment variables, GPUs and MPI settings | ||
--- |