BwUniCluster2.0/Containers - Revision history

P Schuhmacher: /* Start via Slurm */

2023-05-11T08:51:46Z

Start via Slurm

← Older revision		Revision as of 10:51, 11 May 2023
Line 90:		Line 90:
	* <code>--container-mount-home</code> Mounts the home directory into the container		* <code>--container-mount-home</code> Mounts the home directory into the container
	* <code>--container-writable</code> Makes the container filesystem writable (otherwise only the mounted home is writebale)		* <code>--container-writable</code> Makes the container filesystem writable (otherwise only the mounted home is writebale)
	* <code>--container-remap-root</code> Become root in your container. Allows installation of software via e.G apt(ubuntu)		* <code>--container-remap-root</code> Become root in your container. Allows installation of software via e.G apt (ubuntu)

	== FAQ ==		== FAQ ==

P Schuhmacher: /* SLURM Integration */

2023-05-11T08:48:53Z

SLURM Integration

← Older revision		Revision as of 10:48, 11 May 2023
Line 80:		Line 80:

	Download and start Container via pyxis directly:		Download and start Container via pyxis directly:
	*<code>salloc -p dev_single -t 00:10:00 --container-image=~~docker://~~ubuntu --container-name=ubuntu --container-mounts=/etc/slurm/task_prolog:/etc/slurm/task_prolog,/scratch:/scratch</code>		*<code>salloc -p dev_single -t 00:10:00 --container-image=ubuntu --container-name=ubuntu --container-mounts=/etc/slurm/task_prolog:/etc/slurm/task_prolog,/scratch:/scratch</code>
	In this case an enroot Container is created under ~./local/share/enroot/		In this case an enroot Container is created under ~./local/share/enroot/

P Schuhmacher: /* Start via Slurm */

2023-05-11T08:47:19Z

Start via Slurm

← Older revision		Revision as of 10:47, 11 May 2023
Line 80:		Line 80:

	Download and start Container via pyxis directly:		Download and start Container via pyxis directly:
	*<code>salloc -p ~~dev_cpuonly~~ -t 00:10:00 --container-image=docker://ubuntu --container-name=ubuntu --container-mounts=/etc/slurm/task_prolog:/etc/slurm/task_prolog,/scratch:/scratch</code>		*<code>salloc -p dev_single -t 00:10:00 --container-image=docker://ubuntu --container-name=ubuntu --container-mounts=/etc/slurm/task_prolog:/etc/slurm/task_prolog,/scratch:/scratch</code>
	In this case an enroot Container is created under ~./local/share/enroot/		In this case an enroot Container is created under ~./local/share/enroot/

P Schuhmacher: /* SLURM Integration */

2023-05-11T08:39:29Z

SLURM Integration

← Older revision		Revision as of 10:39, 11 May 2023
Line 69:		Line 69:
	Enroot allows you to run containerized applications non-interactively, including MPI- and multi-node parallelism. The necessary Slurm integration is realized via the [https://github.com/NVIDIA/pyxis Pyxis plugin].		Enroot allows you to run containerized applications non-interactively, including MPI- and multi-node parallelism. The necessary Slurm integration is realized via the [https://github.com/NVIDIA/pyxis Pyxis plugin].

			=== Create Container via enroot ===
	NOTE: THIS IS WORK IN PROGRESS!

			* <code>enroot import docker://ubuntu</code>
			* <code>enroot create -n pyxis_ubuntu ubuntu.sqsh</code>
			Adding pyxis_ is a must for the pyxis plugin to work

			=== Start via Slurm ===
			Start existing Container:
			*<code>salloc -p dev_single -t 00:10:00 --container-name=ubuntu --container-mounts=/etc/slurm/task_prolog:/etc/slurm/task_prolog,/scratch:/scratch</code>

			Download and start Container via pyxis directly:
			*<code>salloc -p dev_cpuonly -t 00:10:00 --container-image=docker://ubuntu --container-name=ubuntu --container-mounts=/etc/slurm/task_prolog:/etc/slurm/task_prolog,/scratch:/scratch</code>
			In this case an enroot Container is created under ~./local/share/enroot/

			Note: <code>--container-mounts=/etc/slurm/task_prolog:/etc/slurm/task_prolog,/scratch:/scratch</code> is needed for the plugin to work!! The Container name has to start with pyxis_ for the Plugin to work. When using the second Method this is done automatically. Furthermore when specifying the container name in your slurm Job the pyxis_ has to be omitted.

			All options usable for pyxis can be found via srun --help under "Options provided by plugins:"

			Notable Options:
			* <code>--container-mount-home</code> Mounts the home directory into the container
			* <code>--container-writable</code> Makes the container filesystem writable (otherwise only the mounted home is writebale)
			* <code>--container-remap-root</code> Become root in your container. Allows installation of software via e.G apt(ubuntu)

	== FAQ ==		== FAQ ==

P Weisbrod at 12:44, 24 March 2023

2023-03-24T12:44:53Z

← Older revision		Revision as of 14:44, 24 March 2023
Line 4:		Line 4:
	For example native Docker environments require elevated privileges, which is not an option on shared HPC resources. Docker's "rootless mode" is also currently not supported on our HPC systems because it does not support necessary features such as cgroups resource controls, security profiles, overlay networks, furthermore GPU passthrough is difficult. Necessary subuid (newuidmap) and subgid (newgidmap) settings may impose security issues.		For example native Docker environments require elevated privileges, which is not an option on shared HPC resources. Docker's "rootless mode" is also currently not supported on our HPC systems because it does not support necessary features such as cgroups resource controls, security profiles, overlay networks, furthermore GPU passthrough is difficult. Necessary subuid (newuidmap) and subgid (newgidmap) settings may impose security issues.

	On bwUniCluster the container runtimes '''Enroot''' and '''Singularity''' are supported.		On bwUniCluster the container runtimes '''Enroot''' and '''Singularity/Apptainer''' are supported.

	Further rootless container runtime environments (Podman, …) might be supported in the future, depending on how support for e.g. network interconnects, security features and HPC file systems develops.		Further rootless container runtime environments (Podman, …) might be supported in the future, depending on how support for e.g. network interconnects, security features and HPC file systems develops.

P Weisbrod at 12:44, 24 March 2023

2023-03-24T12:44:37Z

← Older revision		Revision as of 14:44, 24 March 2023
Line 95:		Line 95:
	* [https://slurm.schedmd.com/SLUG19/NVIDIA_Containers.pdf Slurm User Group Meeting 2019 talk]		* [https://slurm.schedmd.com/SLUG19/NVIDIA_Containers.pdf Slurm User Group Meeting 2019 talk]

	= Singularity =		= Singularity/Apptainer =
	Membership in a special group is required to be able to use Singularity. Please refer to the Support channels to request access.
	[[File:singularity_logo.svg\|center\|100px]]		[[File:singularity_logo.svg\|center\|100px]]

Line 102:		Line 101:
	== Usage ==		== Usage ==

	Excellent documentation is provided on the [https://sylabs.io/docs/ Documentation&Examples] page provided by Sylabs~~, the company behind Singularity~~. This documentation here therefore confines itself to simple examples to get to know the essential functionalities.		Excellent documentation is provided on the [https://sylabs.io/docs/ Documentation&Examples] page provided by Sylabs. This documentation here therefore confines itself to simple examples to get to know the essential functionalities.

	Using Singularity usually involves two steps:		Using Singularity/Apptainer usually involves two steps:

	* Building a container image using singularity build		* Building a container image using singularity build

P Schuhmacher: P Schuhmacher moved page BwUniCluster 2.0/Containers to BwUniCluster2.0/Containers: Restructuring bwUniCluster pages into subpages

2022-10-07T07:33:31Z

P Schuhmacher moved page BwUniCluster 2.0/Containers to BwUniCluster2.0/Containers: Restructuring bwUniCluster pages into subpages

← Older revision	Revision as of 09:33, 7 October 2022
(No difference)

M Janczyk: M Janczyk moved page Containers to BwUniCluster 2.0/Containers

2022-05-13T08:48:59Z

M Janczyk moved page Containers to BwUniCluster 2.0/Containers

← Older revision	Revision as of 10:48, 13 May 2022
(No difference)

S Braun: /* ENROOT */

2021-06-25T08:02:19Z

ENROOT

← Older revision		Revision as of 10:02, 25 June 2021
Line 10:		Line 10:
	= ENROOT =		= ENROOT =

	Enroot enables you to run '''Docker containers''' on HPC systems. It is developed by NVIDIA. It is the '''recommended tool''' to use containers on bwUniCluster and integrates well with GPU usage.		Enroot enables you to run '''Docker containers''' on HPC systems. It is developed by NVIDIA. It is the '''recommended tool''' to use containers on bwUniCluster and integrates well with GPU usage and has basically no impact on performance.
	Enroot is available to all users by default.		Enroot is available to all users by default.
	[[File:docker_logo.svg\|center\|100px]]		[[File:docker_logo.svg\|center\|100px]]

S Braun: /* Additional resources */

2021-06-25T08:01:46Z

Additional resources

← Older revision		Revision as of 10:01, 25 June 2021
Line 91:		Line 91:
	Documentation: [https://github.com/NVIDIA/enroot/blob/master/doc https://github.com/NVIDIA/enroot/blob/master/doc]		Documentation: [https://github.com/NVIDIA/enroot/blob/master/doc https://github.com/NVIDIA/enroot/blob/master/doc]

			Additional information:
	~~Additional information:~~ [https://archive.fosdem.org/2020/schedule/event/containers_hpc_unprivileged/ FOSDEM 2020 talk] + [https://archive.fosdem.org/2020/schedule/event/containers_hpc_unprivileged/attachments/slides/3711/export/events/attachments/containers_hpc_unprivileged/slides/3711/containers_hpc_unprivileged.pdf slides]		* [https://archive.fosdem.org/2020/schedule/event/containers_hpc_unprivileged/ FOSDEM 2020 talk] + [https://archive.fosdem.org/2020/schedule/event/containers_hpc_unprivileged/attachments/slides/3711/export/events/attachments/containers_hpc_unprivileged/slides/3711/containers_hpc_unprivileged.pdf slides]
			* [https://slurm.schedmd.com/SLUG19/NVIDIA_Containers.pdf Slurm User Group Meeting 2019 talk]

	= Singularity =		= Singularity =