IT hands-on

To limit the use of <i> CPU -150m- </i> and <i> memory -1024- </i> resources of an " nginx " container , we could use the below command for example: " 8080 &q

The docker daemon is usually run as a service on the local machine, we could check it using the below command: We can communicate with the docker daemo

Storage drivers deal with the images, the  UFS filesystem - <i> Union File System</i> -, storage, docker image layers and the COW - <i> Copy On write</i> - system for

For administrative reasons a container might need to have access to the processes running on the host machine or on another container on the same host

UTS namespaces deal with hostnames  and domain names . If we isolate the UTS namespace of a process, its host name becomes independent from the hostname o

<b><i> Attaching a volume to multiple containers:</i></b><b><i></i></b><b><i> </i></b> We start by running a container named "<i> cont-one</i> ", using a debian image. We also use a volume named

<b><i> Access to the volume of a container from a different container:</i></b><b><i></i></b><b><i> </i></b><b><i></i></b> We use the below command, to first create a "<i> vol-deb "</i> volume  for our container

<b><i></i></b> <b><i> Docker and the "host" network:</i></b> In the " host " network setup, the container will use the IP address of the network stack of its host,

The host's RAM could offer a high speed temporary storage for container's data through the " tmpfs " filesystem. A tmpfs storage can

<b><i></i></b> <b><i> Docker Networking:</i></b> In docker , each container has its own networking stack .  This isolation is possible through the use of the Linux kernel network names

<b><i></i></b> <b><i> Privileged containers:</i></b> Privileged containers benefit from extended rights, that gives them access to devices, system directories, ... on the host. From

Usually and unless mentioned in the Dockerfile , the image gets build and runs with root privileges inside the container.<b><i> Running a container with non-r