DOCKER, PODMAN AND KUBERNETES

Which Docker training fits your task?

Docker training should match your next task, prior knowledge and working environment. Compare courses for Docker, Podman and an introduction to Kubernetes by content, prerequisites, format and published dates. We can also help teams choose in a personal consultation.
Choose a workshopDiscuss team training

Understanding Docker

Which Docker training covers which step?

From the Dockerfile through the image and registry to the running container, this chain describes the path into operation. Every training and course on this page starts at one of these steps.

Technical basis: Open Container Initiative

FROM BUILD TO OPERATION

Building blocks from image build to container operation

Each training starts at one step

  1. 01

    Image build definition

    Defines the base, dependencies and build steps

    Course code: DW1Introduction to Docker
  2. 02

    Image

    Bundles layers and startup configuration

    Course code: DW1Introduction to DockerCourse code: DW8Introduction to Podman
  3. 03

    Registry

    Stores images for distribution and retrieval in Harbor or GitLab Registry

    Course code: DW14Introduction to GitLab CI/CD
  4. 04

    Container

    Runs a process from an image

    Course code: DW1Introduction to DockerCourse code: DW8Introduction to Podman

RESPONSIBILITIES AROUND CONTAINERS

What the runtime handles and what remains separate

Runtime and engine
Docker builds images and runs containers on one host. It also manages networks and volumes for individual services or services connected with Compose.
Roles of supporting tools
Additional effort begins with multiple hosts, coordinated rollouts and scaling. For these tasks, Kubernetes orchestrates containerised applications in a cluster.

Where containers help in practice

Containers help applications with defined dependencies run consistently across environments. Compose connects related services on one host.

Where additional work arises

Containers still require maintained images, data backups, access controls and monitoring. A move is worthwhile when it solves a concrete operational problem.

TASKS IN CONTAINER OPERATIONS

What work does using containers involve?

  • Understand Linux foundations and runtimesKernel, user mapping, runtimes, OCI

    Linux foundations and runtimes are the basis for anyone who needs to understand containers on hosts or in clusters.

    • Namespaces and cgroups separate process, network, and mount views and limit CPU and memory. Containers still share the host kernel.
    • User mapping determines access to volumes partly through numeric UIDs and GIDs, especially in rootless operation.
    • Runtimes differ by layer: Docker and Podman manage containers on a host, while Kubernetes uses CRI runtimes such as containerd or CRI-O.
    • OCI standardises the image format and runtime specification but does not make tool features fully interchangeable.

    Introduction to Linux (DW18) teaches the Linux foundations for further container work.

    View in the catalogue
  • Build images for their intended useDockerfile, build cache, minimal base, multi-arch

    Image builds matter to anyone packaging applications and dependencies reproducibly for use.

    • A Dockerfile or Containerfile describes how a base image, application, and dependencies become an image.
    • Layers and the build cache affect build time and size.
    • Multi-stage builds keep build tools out of the runtime image.
    • Small or distroless images often contain no shell, which changes troubleshooting.

    Introduction to Docker (DW1) covers these build fundamentals. There is currently no dedicated course for multi-architecture builds.

    View in the catalogue
  • Publish images and operate registriesTags and digests, access controls, retention, mirroring

    Image distribution concerns teams that provide images across development and operations or manage a registry.

    • Tags give image revisions readable names.
    • Digests identify the exact content of an image.
    • Registries make images available for development and operations.
    • Registry operation requires teams to manage access, storage, retention, and mirroring.

    Introduction to GitLab CI/CD (DW14) covers building and publishing. We do not currently offer a dedicated course on registry operation.

    View in the catalogue
  • Run containers on a hostCompose, networks, troubleshooting, development environments

    Host operation is for anyone who runs and diagnoses individual containers or connected services.

    • Compose describes services, networks, and volumes on one host, such as an application with its database.
    • Logs, health checks, ports, and resource limits support operations and troubleshooting.
    • Dev Containers provide development environments as containers.
    • Short-lived test containers are another use case.

    Introduction to Docker (DW1) covers Docker and Compose. Introduction to Podman (DW8) focuses on Podman, rootless operation, and systemd.

    View in the catalogue
  • Secure images and running containersVulnerabilities, supply chain evidence, rootless, requirements

    Container security concerns teams that assess vulnerabilities, provenance, and privileges for images and running containers.

    • Image scans report known vulnerabilities in base images and dependencies that teams must assess and prioritise.
    • SBOMs and signatures document components and support provenance checks.
    • Rootless operation reduces privileges on the host but does not replace careful user, volume, and permission configuration.

    Preparation for the Kubernetes and Cloud Native Security Associate (KCSA) Exam (DW25) and Preparation for the Certified Kubernetes Security Specialist (CKS) Exam (DW7) cover supply chain evidence in a Kubernetes security context. There is currently no dedicated container supply chain course.

    View in the catalogue
  • Distribute applications within a clusterWorkloads, scheduling, connectivity

    Cluster orchestration is for teams that distribute and operate container workloads across multiple nodes.

    • Kubernetes and OpenShift schedule container workloads across cluster nodes and maintain the desired state.
    • Deployments, Services, scaling, and access controls belong to this area.
    • Image builds and registry operation remain separate tasks.

    Introduction to Kubernetes (DW2) introduces deployment, Kubernetes Advanced (DW3) develops operational skills, and Introduction to Red Hat OpenShift (DW13) covers OpenShift-specific work.

    View in the catalogue

IMAGE AND DISTRIBUTION

, , , ,

Image
An image is an immutable package of filesystem layers and startup configuration. It is the template for containers and keeps the application and its dependencies consistent across environments.
Layer
A layer is an immutable filesystem layer within an image. Images can share layers, making storage and transfer more efficient and making the order of build steps relevant.
Tag
A tag is a readable, changeable name for an image revision in a repository. Because the same tag can later point to different content, a digest is more suitable for reproducible delivery.
Registry
A registry is a service for storing and distributing images. Teams publish images there so development, CI, and operational environments can retrieve them in a controlled way.
Digest
A digest is a unique identifier calculated from image content. Unlike a changeable tag, it allows the exact same content to be retrieved and verified again.

CONTAINERS IN OPERATION

, , , ,

Container
A container is a running process started from an image with an isolated view of parts of the system. It shares the host kernel, while namespaces and cgroups separate its environment and resources.
Volume
A volume stores data outside a container's writable layer. It preserves data beyond the container lifecycle and requires suitable access, backup, and recovery rules.
Network
A container network connects containers to each other and, where needed, to external services. Names, addresses, and rules determine which services can communicate and which connections remain isolated.
rootless
Rootless operation runs containers without root privileges on the host. This reduces privileges but still requires careful configuration of users, volumes, and access permissions.
Runtime
A runtime executes containers, although the term covers different layers. Low-level runtimes such as runc create processes, while Kubernetes communicates through CRI with runtimes such as containerd or CRI-O.

STANDARDS AND SECURITY

, , , ,

OCI
The Open Container Initiative defines open specifications for image formats and container runtimes. These standards support interoperability between tools but do not make their features identical.
Namespace
A Linux namespace gives processes an isolated view of resources such as processes, networks, or mounts. It is a core kernel mechanism that separates container environments from the host and from each other.
SBOM
A software bill of materials lists the components and dependencies in a software artefact. It helps teams identify affected components and document supply chain information transparently.
Signature
A digital signature cryptographically links an artefact to an identity and makes later changes detectable. For images, it supports provenance checks but does not replace assessment of the content.
Image scan
An image scan compares image components with data about known vulnerabilities. The result is evidence for teams to assess and prioritise, not automatic proof that an image is secure.

Which task should the training prepare you for?

Choose your task, prior experience and target environment. The finder maps your answers to a course and flags missing foundations or gaps in the catalogue.

Start the workshop finder

STARTING POINTS AT A GLANCE

Which starting point fits: Docker, Podman or Docker with Kubernetes?

The Docker introduction focuses on images and Compose. The Podman workshop covers rootless operation, pods and systemd. If Kubernetes is already part of the learning goal, the compact workshop combines Docker fundamentals with the Kubernetes introduction.

GETTING STARTED WITH DOCKER

Beginner

Introduction to Docker

2 daysLive onlineCourse code: DW1

Basic Linux knowledge, terminal experience and familiarity with an editor are required. You do not need previous Docker or programming knowledge.

Your learning path

Before: Introduction to Linux

Course code: DW18

Now: Introduction to Docker

Create Docker images and run applications with networks, volumes and Compose

Then: Introduction to Kubernetes

Course code: DW2

View workshop

GETTING STARTED WITH PODMAN

Beginner

Introduction to Podman

You need basic Linux terminal skills and experience with an editor. Docker practice makes getting started easier, but is not a prerequisite.

3 daysCourse code: DW8View workshop

LEARN DOCKER WITH KUBERNETES

Beginner

Docker and Kubernetes Essentials

You know Linux and the command line and have a basic understanding of development or administration. Docker and Kubernetes are covered from the ground up.

5 daysCourse code: DW4View workshop

COURSE CHOICES WITH CLEAR BOUNDARIES

Compare courses by task and prior knowledge

See the audience, prerequisites, duration, level, price and possible follow-on courses side by side. "Not the right fit if" shows when another starting point is more suitable.

STARTING POINT

Suited for

DW1 Introduction to Docker
Create your own Docker images and run applications with Docker Compose
DW8 Introduction to Podman
Build images and run rootless containers in a Podman environment
DW4 Docker and Kubernetes Essentials
Learn container fundamentals and then deploy applications on Kubernetes

Not the right fit if

DW1 Introduction to Docker
you want to learn Podman specifically or cover Docker and Kubernetes in the same course
DW8 Introduction to Podman
you want to learn Docker and Docker Compose specifically or cover Kubernetes operations
DW4 Docker and Kubernetes Essentials
you want to learn Docker or Podman exclusively and do not want to cover Kubernetes fundamentals

Prerequisites

DW1 Introduction to Docker
Linux and terminal basics plus editor skills; no programming knowledge or Docker experience required
DW8 Introduction to Podman
Linux and terminal basics plus editor skills; Docker experience helpful, but optional
DW4 Docker and Kubernetes Essentials
Linux and terminal basics plus a basic understanding of software development or system administration

COURSE DETAILS & LEARNING PATH

Duration

DW1 Introduction to Docker
2 days
DW8 Introduction to Podman
3 days
DW4 Docker and Kubernetes Essentials
5 days

Level

DW1 Introduction to Docker
Beginner
DW8 Introduction to Podman
Beginner
DW4 Docker and Kubernetes Essentials
Beginner

Price

DW1 Introduction to Docker
€1,110.00per person, plus 19% VAT
DW8 Introduction to Podman
€1,665.00per person, plus 19% VAT
DW4 Docker and Kubernetes Essentials
€2,775.00per person, plus 19% VAT

Possible next step

DW1 Introduction to Docker
Introduction to Kubernetes for first cluster tasks or Introduction to GitLab CI/CD for image pipelines
DW8 Introduction to Podman
Next: Introduction to Kubernetes; with Kubernetes fundamentals already in place, also Introduction to Red Hat OpenShift
DW4 Docker and Kubernetes Essentials
Advanced Kubernetes for Kubernetes operations or Introduction to GitLab CI/CD for automated image pipelines

Workshop pages

Agenda & dates

TRAINING FOR CONTAINER WORK

Courses for containers, image delivery and clusters

Depending on the task, start with Linux, Docker or Podman, automate image delivery or move into cluster operations. The security courses build on Kubernetes knowledge; their prerequisites are shown with each course.

Workshop index

11 published workshops, 4 learning goals
1 workshop

Build prerequisite knowledge for container work

If Linux and the terminal are new to you, start here. Introduction to Linux (DW18) covers the shell, permissions, processes, services and networking. Containers are not part of its agenda.

  • DW18Introduction to LinuxLearn Linux fundamentals covering the shell, permissions, processes, services and networking as preparation for container work; no container topics in the course3 days
3 workshops

Understand images and containers

Choose Docker or Podman to match your working environment. The compact course connects Docker fundamentals directly with an introduction to Kubernetes.

  • DW1Introduction to DockerCreate Docker images and run applications with networks, volumes and Compose2 days
  • DW8Introduction to PodmanBuild images with Podman and operate rootless containers using pods and systemd3 days
  • DW4Docker and Kubernetes EssentialsBuild Docker images, connect services with Compose and deploy applications on Kubernetes5 days
4 workshops

Deliver and verify images

In Introduction to GitLab CI/CD (DW14), you automate builds, publishing and scans in GitLab pipelines. SBOMs, signatures and policies appear only in advanced Kubernetes security courses.

  • DW14Introduction to GitLab CI/CDAutomate image builds, tagging, publishing and vulnerability scans in GitLab pipelines2 days
  • DW25KCSA Exam PreparationAssess base images and read SBOMs in the Kubernetes course for KCSA preparation; basic Kubernetes knowledge required3 days
  • DW7CKS Exam PreparationPractise image signing, SBOM generation and CVE scans in the Kubernetes course for CKS preparation; Kubernetes administration experience and CKA required4 days
  • DW30Introduction to KyvernoBuild on Kubernetes experience to enforce image signature requirements and permitted registries through Kyverno policies3 days
3 workshops

Run container applications in clusters

These courses use images in Kubernetes or OpenShift. They range from first deployment to operations, scaling and platform work.

  • DW2Introduction to KubernetesDeploy container images through Kubernetes deployments and expose applications using services3 days
  • DW3Advanced KubernetesDevelop containerised application operations through Kubernetes scaling, access controls and monitoring2 days
  • DW13Introduction to Red Hat OpenShiftOperate containerised applications on OpenShift with deployments, routes and rollout strategies3 days

This catalogue lists only published workshops with their own detail page.

YOUR LEARNING PATH TO THE CLUSTER

From Linux foundations to the cluster

This learning path is for teams that plan to run containers with Kubernetes. Start with Linux only if those foundations are missing. Then choose Docker or Podman to match your working environment; existing knowledge may let you join at a later stage.

Recommended route

Suggested route, not a fixed sequence

  1. 01

    LINUX FOUNDATIONS

    Work confidently with Linux

    • FOUNDATION IF NEEDEDIntroduction to LinuxLearn and practise Linux shell skills, permissions, processes, services and networking; this course does not include container topics.Beginner3 daysCourse code: DW18
  2. 02

    DOCKER OR PODMAN

    Build Docker or Podman foundations

    • IMAGES AND COMPOSEIntroduction to DockerCreate Dockerfiles and practise how containers, networks and volumes work together with Compose.Beginner2 daysCourse code: DW1
    • ROOTLESS AND SYSTEMDIntroduction to PodmanBuild images with Podman, run containers without root privileges and practise pods and systemd integration.Beginner3 daysCourse code: DW8
  3. 03

    APPLICATIONS ON KUBERNETES

    Start with Kubernetes or deepen operations

    • KUBERNETES ENTRYIntroduction to KubernetesIntegrate container images and deploy applications in a Kubernetes cluster using Deployments and Services.Beginner3 daysCourse code: DW2
    • WITH KUBERNETES FUNDAMENTALSAdvanced KubernetesDeepen your knowledge of scaling, access rules and monitoring for running apps in a Kubernetes cluster.Intermediate2 daysCourse code: DW3

The order is a guide. If your Linux foundations are in place, start directly with Docker or Podman. If Kubernetes is already the destination and you want to learn Docker fundamentals together with the Kubernetes introduction, the compact workshop combines both topics.

View the Kubernetes learning path

VOICES FROM THE WORKSHOPS

What participants say about Docker training

The following feedback comes from the Docker introduction and the Podman workshop. The quotes refer specifically to structure, exercises, the learning environment and learning outcomes.

DW1 Introduction to Docker

„I really enjoyed the Docker workshop at DevNinjas! The content was well structured and clearly explained, even for beginners like me. The mix of theory and hands-on exercises was especially helpful for trying Docker directly. By the end, I was able to build my own images, configure containers and set up networks. Absolutely recommended for anyone who wants to learn Docker!“

Pascal Schunk

OEDIV, Introduction to Docker

Participant voice on DW1

„Competent instructor. Individual approach to problems and topics. Interesting structure. Highly recommended to get an in-depth insight into the Docker world. The workshop was definitely worth it. Thanks!“

H. Hillebrand

PFSt NRW, Introduction to Docker

Participant voice on DW8

„I can really only give praise. Providing every participant with their own Coder-based playground in this digital age is simply brilliant.“

Ronny K.

Introduction to Podman

Vincent Sturm - DevNinjas

Choose a container workshop for your IT team

Vincent Sturm

Key Account Manager

Tell us what your team works with today and which task participants should take on after the training. We recommend a workshop and say clearly if they need additional foundations first. For specific requirements, we plan a separate agenda.

vincent@devninjas.io
+49 221 9865099-4
WhatsApp Chat

Frequently asked questions about Docker and container training

Docker, Podman or Docker with Kubernetes: which course fits?

Introduction to Docker suits Dockerfiles and Compose projects; Introduction to Podman suits rootless containers in Red Hat environments; Docker and Kubernetes compact teaches Docker followed by Kubernetes.

Introduction to Docker (DW1) covers images, networks, volumes and Docker Compose. Introduction to Podman (DW8) also covers pods and systemd. Docker and Kubernetes compact (DW4) combines the two sets of foundations in one course.

What experience do I need before taking Docker training?

The introductory Docker, Podman and Docker with Kubernetes courses require Linux and terminal basics, plus familiarity with a text editor or IDE.

You should be able to navigate files and directories and run commands. Introduction to Docker requires no container or programming experience. Container knowledge helps with Podman, but no Podman experience is needed. Basic networking and an understanding of application structure help with the compact course but are not prerequisites. Introduction to Linux (DW18) covers missing terminal foundations.

Do I need to install Docker or Podman for training?

You do not need to install Docker or Podman locally for the course. You work in the browser-based DevNinjas Dojo with exercise resources assigned to you alone. The workshop overview explains the general live online format.

Can we bring our Dockerfiles or Compose projects to team training?

We can include your Dockerfiles or Compose projects in Docker team training by prior agreement.

Before preparing the proposal, we agree whether your example fits the learning goal and how much of the agenda it can occupy. We use prepared or anonymised examples; production access and confidential data are not needed. Public workshops use prepared scenarios. We agree your own examples when planning corporate training.

What should I learn after introductory Docker training?

After introductory Docker training, choose according to your next task: automating image builds or running applications in a Kubernetes cluster.

For automated builds and publishing images to a registry, Introduction to GitLab CI/CD (DW14) fits if you have basic Git skills. For cluster operations, the learning path takes you from a Kubernetes introduction to suitable advanced courses.

Should I learn Docker or Kubernetes first?

Start with Docker if you want to build container images; if your task is deploying or operating applications, you can start directly with the Kubernetes introduction.

Container knowledge helps when learning Kubernetes, but it is not a prerequisite. If you want to learn both foundations together, Docker and Kubernetes compact (DW4) combines them in five days.

Which container topics have no dedicated course?

DevNinjas currently has no dedicated public course on Linux for containers, registry operations, supply-chain attestations outside the Kubernetes courses, or multi-architecture builds.

Linux for containers is in preparation. No dedicated course has been announced for the other topics. For corporate training, we assess which parts suit your learning goal and can be included in the agenda.

How long are the Docker and Podman courses?

At DevNinjas, Introduction to Docker takes two days, Introduction to Podman three days, and Docker and Kubernetes Essentials five days. Public courses run live online on consecutive days, usually from 09:00 to 16:00.

The schedule lists the available courses. Plan for the days of your selected course as one continuous training period.