...
 
Commits (2)
......@@ -89,7 +89,7 @@
"metadata": {},
"outputs": [],
"source": [
"!singularity exec -B /data neurodebian-neurodebian-master-latest.simg dcm2nii"
"!singularity exec neurodebian-neurodebian-master-latest.simg dcm2nii"
]
},
{
......@@ -105,6 +105,22 @@
"source": [
"A container is a standard unit of software that packages up code and all its dependencies so the application runs quickly and reliably from one computing environment to another. A container image is a lightweight, standalone, executable package of software that includes everything needed to run an application: code, runtime, system tools, system libraries and settings.\n",
"\n",
"If you take a look at the content of a container, they look like a complete OS system (run the next cell), but a container image only contains the dependencies for the software from the OS environment"
]
},
{
"cell_type": "code",
"execution_count": null,
"metadata": {},
"outputs": [],
"source": [
"!singularity exec neurodebian-neurodebian-master-latest.simg ls /"
]
},
{
"cell_type": "markdown",
"metadata": {},
"source": [
"Containers use the host system's kernel, and can access its hardware more directly. When you run a process in a container it runs on the host system, directly visible as a process on that system. Unlike a Virtual Machine, container is a virtualization at the software level, whereas VMs are virtualization at hardware level. If you are interested in finding out more differences between VM and a container, go to this [link](https://www.electronicdesign.com/dev-tools/what-s-difference-between-containers-and-virtual-machines)"
]
},
......