Docker: Containerisation
Images, containers, volumes, networks and Docker Compose. Package and deploy your applications in a portable way.
- Understand containerisation
- Build optimised images
- Manage volumes and networks
- Orchestrate with Docker Compose
- Ship an application in a container that runs identically in dev, test and prod
- Drastically cut the "it works on my machine" problem: the environment is packaged with the app
- Compose a complete application stack (web + database + cache) with a single docker-compose file
- Optimise your images for fast builds and lightweight production deployments
The programme
Day 1 - Fundamentals
- Containers vs VMs: isolation, namespaces, cgroups
- Images and Dockerfile: layers, cache, multi-stage builds
- Registries: Docker Hub, GHCR, private registry
- Volumes and bind mounts: data persistence
- Workshop: containerise a Python/Node application and publish it
Day 2 - Compose, networking & production
- Docker networks: bridge, host, overlay
- Docker Compose: services, dependencies, healthchecks
- Security best practices: non-root user, Trivy scan, secrets
- Image optimisation: size, .dockerignore, distroless
- Workshop: multi-service stack with Compose, monitoring and vulnerability scanning
Who is this for
Developers, ops and any team delivering applications.
Prerequisites
- Linux and command line basics
Format
Frequently asked questions
Which version of Docker is taught?
Docker Engine v27 (the stable version at the date of the session). Docker Desktop is also covered for developers on macOS and Windows.
Does the course cover Docker Swarm?
No. Docker Swarm has reached end of life and has been replaced by Kubernetes in production. The course focuses on Docker alone (build, run, networks, volumes, compose) and naturally prepares you for the Kubernetes course.
Is the course eligible for OPCO or CPF funding?
No. Sphinx-Digital is not Qualiopi certified and is not listed on Mon Compte Formation. The course is invoiced directly to the company or the individual, with no external funding.
What is the difference between the public (inter-company) and in-company formats?
In the public format, you join a session with participants from other companies (3 to 10 people). In-company, we run a session dedicated to your team, on your site or remotely, with content adapted to your context. In-company pricing is available on quote.
Remote or on-site: what are the practical differences?
Content and labs are identical. Remotely, labs run on cloud environments accessible from a browser, with nothing to install. On-site, you provide the workstations; labs can run in the cloud or locally depending on your infrastructure.
How many participants per session?
3 to 10 participants at most. This deliberate limit ensures everyone can ask questions, adapt the exercises to their context and get a detailed answer.
What is the evening format?
The evening format spreads the same course over 4 sessions of 3.5 hours (14 hours in total), in the evening from 6:30 pm to 10:00 pm. Same content, same labs, same price, so you can build skills without taking days off.
How does payment work?
Courses are invoiced on quote, by bank transfer. Payment in instalments is possible. We issue a training agreement for companies that want their training department to cover the cost.
Interested in this course?
Join the next session or request a tailored in-company session.
What participants say
Not sure this course fits your context?
A 20-minute call to take stock before you enrol, with no sales pitch.