This page is actively maintained by the Grid'5000 team. If you encounter problems, please report them (see the Support page). Additionally, as it is a wiki page, you are free to make minor corrections yourself if needed. If you would like to suggest a more fundamental change, please contact the Grid'5000 team.
Docker is a software technology that provides operating-system-level virtualization. In this page, we present some tools that are specifically designed to use Docker on Grid'5000.
- 1 Installing Docker from a node
- 2 Using docker-machine and docker-g5k
- 3 Managing Docker images
- 4 Avoid network conflict
- 5 Nvidia-docker
Installing Docker from a node
You can install and use Docker from a node with the standard environment by following these instructions:
- Reserve a node
(you can also use option
-t deploy and Kadeploy if you prefer)
- Install Docker
The script g5k-setup-docker, available from the standard environment, installs Docker locally and make Docker commands available without user needing to log out (by giving read write permissions to the file /var/run/docker.sock)
g5k-setup-docker can also call sudo-g5k internally, so it is possible to simply type
If you want to simply install Docker, without changing the permissions of /var/run/docker.sock (note that in this case you must log out and reconnect before using Docker commands), you can type
- Run Docker
You can now check that Docker is up and running
- Note for the environments nfs and big
In addition to the standard environment, g5k-setup-docker works with the environments debian10-x64-nfs and debian10-x64-big (and with debian9-x64-nfs and debian9-x64-big. Note that the directory containing g5k-setup-docker is not defined in the $PATH of these environments: you must so call the script from its full path
Using docker-machine and docker-g5k
The Spirals Team in Lille developped two tools to ease Docker usage on Grid'5000:
- a docker-machine driver
- the docker-g5k program
Provision a node with docker-machine
The driver for docker-machine allows you to reserve a node on Grid'5000 and to install a Linux image and Docker Engine on it, from your computer and in one single command.
The reserved node is then available from commands like
docker-machine ssh (standard ssh commands don't work when nodes are reserved with docker-machine).
Create a Swarm with docker-g5k
The docker-g5k program allows you to reserve several nodes, possibly on different sites, and to install a Linux image and Docker Engine on each node, in one single command. This command configures a Swarm, i.e. a set of Docker containers distributed over several nodes that communicate with each other.
Managing Docker images
One difficult aspect of using Docker is efficient images management, as (1) it is often required to load such images on many nodes simultaneously; (2) Grid'5000 connection to the internet is limited to 1 Gbps. The following strategies are recommended to manage Docker images:
Use docker load/save
To load and save images quickly, we encourage you to use
docker load and
docker save commands, with .tar docker images stored in your Grid'5000 home. Users home are NFS mounted, with good network performance.
You can also use
docker load command instead of retrieving the image from Docker Hub, when deploying a Swarm with docker-g5k.
- Example with docker-g5k
Give read rights to your image
Deploy three Docker nodes in Nancy (activate the Grid'5000 VPN before launching this command)
Load Alpine image on each node
Use Inria private registry
The Inria registry has been closed by the end of 2019/beg. 2020.
As an alternative one can use gitlab.inria.fr to host docker images related to a git project, but this cannot be compared to the functionalities provided by a normal Docker registry.
Use a persistent virtual machine to host your registry
If you want to benefit from a private registry with good network performance, and are ready to manually install your own registry, you can request a Persistent Virtual Machine. You can look at Harbor or Portus open source projects, in order to install your own registry.
Avoid network conflict
The default network used by docker is 172.16.0.1/16 which is use internally on Grid'5000 thus this can be a source of conflict.
If you want to avoid any conflict you can set an other network. On debian you will have to edit /etc/default/docker and specify the network you want to use like this:
(You don't need to run