Target Picture from Day One
The map shows every building block of the stack. Before each chapter, it is clear which building block is being created now and what it is for.
Corporate Training · Containers · 3 Days
In three days, your team learns to move applications into containers with Podman and Docker and run them properly. Participants rebuild the order shop of a fictional company step by step – from the first container start to their own hardened images and a stack of shop, catalog and database that starts automatically and can be updated in minutes.
Learning Objectives
After three days, participants do not just know the Podman and Docker commands – they have moved a multi-part application into containers themselves, secured it and set it up for production.
Target Audience
The training is designed for administrators, DevOps engineers and developers who have not built their own containers yet or have used Docker by following online guides.
No container experience is needed.
Tools
The course uses Podman, the standard tool on enterprise Linux today, daemonless and rootless. Everything you learn applies to Docker as well: the commands are nearly identical, and differences and migration paths are covered explicitly. The lab runs on Podman, Docker is compared on the slides.
The Hands-On Project
Clusterhausen Waffle Works runs its order shop WaffelOrder on a single server behind the bakery, set up years ago and untouched since. Every new version means an evening of manual work, test and production never look the same, and nobody dares to update the operating system.
Your team takes over: on day one the shop runs in a container, on day two you build your own images for shop, catalog and database and connect them, on day three you make the stack production-ready – hardened, starting automatically, easy to update. Finally, you generate a Kubernetes manifest from it and see where the next step leads.
The map shows every building block of the stack. Before each chapter, it is clear which building block is being created now and what it is for.
A container will not start, a port is taken, a memory limit kicks in. The team tracks down the cause with logs and inspection and fixes it before it ever shows up in production.
The first exercises provide close guidance; later, the sheets only define the goal and the acceptance criteria. Participants solve the finale largely on their own.
For every exercise, all Containerfiles and Compose files are available as a ready-made restore point. Anyone who gets stuck picks it up and is right back in.
Agenda
Day one brings the shop into a container, day two builds the whole application from your own images, and day three makes it production-ready. Every chapter leads into an exercise that moves the company’s stack a step forward.
We adapt the order and depth to the group’s prior knowledge and pace. On request, we set priorities, such as extra time for security, migrating from Docker to Podman or examples from your environment.
Lab Environment
Every participant works in their own fully prepared environment with all the tools used in the course. The required base images are preloaded, so the exercises start without waiting.
Nobody shares a system. Everyone can start and delete containers and provoke errors without disturbing anyone else.
The environment is conveniently accessible via the browser. No local installation is needed, and your IT department does not have to open anything up.
Podman, Buildah, Skopeo, an image scanner and an editor with support for Containerfiles and Compose files are set up.
All exercises are run through completely in the lab environment beforehand, including the deliberately built-in failure scenarios.
After every exercise, all Containerfiles and Compose files are available as a restore point, so participants can rejoin at any time.
Materials
All chapters with our own diagrams, overview tables and a side-by-side comparison of Podman and Docker for easy reference.
Every exercise with a goal, prediction checks and tested Containerfiles as the reference solution.
Short reviews on the course mornings reinforce what was covered the day before.
All Containerfiles, Compose files and Quadlet units created during the course serve as templates for your own applications.
One hour for your practical questions, two to four weeks after the course. Included in the price of every training.
Formats
The training takes place on your premises. Your team learns together and brings in questions about its own applications directly.
Live instruction with joint exercise phases and direct support in each participant’s own environment – ideal for distributed teams.
We align focus areas and examples with your environment, such as security, migrating from Docker to Podman or running your own applications.
Your team already works with containers and wants to dive deeper into a specific topic – such as image hardening, rootless operation or autostart with Quadlet? Then a tailored workshop is the right fit.
After the course
The real work starts after the course. That is why every training includes an Ask the Trainer session: two to four weeks after the course, we meet online for one hour. Your participants send in the questions that came up while applying what they learned in your environment. That leaves the session free for what matters: specific answers for your systems, not the textbook case. The session is included in the price.
Pricing
3 days · €5,950 net for your team of up to 8 participants
includes materials, lab environment and Ask the Trainer session, plus travel and accommodation for on-site delivery
See the training overview for all terms.
Bundle offer
Both courses booked together: €9,950 net instead of €11,900, six days for the price of five. The courses run as two separate dates at least two weeks apart, both within six months, for the same team of up to 8 participants. Each course includes its own Ask the Trainer session, so the one from the container course falls right between the two dates.
Request bundleFAQ
Request
Briefly tell us the format and preferred time frame. We will get back to you with a proposed date and an individual quote. Your request is non-binding.
Your message has reached us. We will get back to you shortly with a proposed date and a quote for the container training.
More Training
Next step: Kubernetes training
The next step: the platform team brings the same shop into the cluster – from the first pod to a hardened, reachable deployment.
5 daysThe company’s server landscape takes shape: the automation team sets up Linux and Windows servers with Ansible – all the way to patch day across all systems.
3 daysThe growing business gets monitoring: tap into data sources, alert the right way and keep operations in view.
The teaching concept, the lab environment and the formats of all courses at a glance.