From 4f3c7b55a7247f17a18b5c8561951619ab9e6f03 Mon Sep 17 00:00:00 2001 From: Norman Koch <norman.koch@tu-dresden.de> Date: Wed, 20 Oct 2021 12:01:29 +0200 Subject: [PATCH] added x86 to virtual_machine_tools.md --- .../docs/software/virtual_machines_tools.md | 19 +++++++++++++++---- 1 file changed, 15 insertions(+), 4 deletions(-) diff --git a/doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md b/doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md index 0b03ddf92..aaf73acd3 100644 --- a/doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md +++ b/doc.zih.tu-dresden.de/docs/software/virtual_machines_tools.md @@ -35,14 +35,19 @@ in which case you'd need to change that when moving to ZIH systems. ## Build a Singularity Container in a Job -To build a Singularity container on ZIH systems simply run: +To build a Singularity container for the power9-architecture on ZIH systems simply run: ```console marie@login$ buildSingularityImage --arch=power9 myContainer.sif myDefinition.def ``` -This command will submit a batch job and immediately return. Note that while Power9 is currently -the only supported architecture, the parameter is still required. If you want it to block while the +To build a singularity image on the x86-architecture, run: + +```console +marie@login$ buildSingularityImage --arch=x86 myContainer.sif myDefinition.def +``` + +These commands will submit a batch job and immediately return. If you want it to block while the image is built and see live output, add the option `--interactive`: ```console @@ -99,12 +104,18 @@ needs to be re-generated on every script run. ## Start a Job in a VM Especially when developing a Singularity definition file it might be useful to get a shell directly -on a VM. To do so simply run: +on a VM. To do so on the power9-architecture, simply run: ```console startInVM --arch=power9 ``` +To do so on the x86-architecture, run: + +```console +startInVM --arch=x86 +``` + This will execute an `srun` command with the `--cloud=kvm` parameter, wait till the VM is ready, mount all folders (just like `buildSingularityImage`, see the Filesystem section above) and come back with a bash inside the VM. Inside that you are root, so you can directly execute `singularity -- GitLab