User-defined Playground

kubeadm (with Docker) Playground

Márk Sági-Kazár
by  Márk Sági-Kazár · on
Kubernetes

A single-machine playground to experiment with kubeadm, using Docker as the container runtime.

kubeadm (with Docker) playground: A single-machine playground to experiment with kubeadm, using Docker as the container runtime.
Machines & network
2 VMs · 8 vCPU · 16GiB RAM
Playground host Internet NAT MASQUERADE local (bridge) 172.16.0.0/24 gw 172.16.0.1/24eth0eth0
VM
vCPU ·
eth0
/
oci://ghcr.io/sagikazarmark/iximiuz-labs/playgrounds/kubeadm-docker/dev-machine:live@sha256:361aa783599893229cc9e5e43e537dc6bfb24f1709a56fd9a0fb7eacee89dfa1
VM
vCPU ·
eth0
/
oci://ghcr.io/sagikazarmark/iximiuz-labs/playgrounds/kubeadm-docker:live@sha256:84fd333c3218c445aa1a8b56f6edebeec43ccc7bfbd906ce804d039d3ab85c07
About

🔧 System Components

  • kubelet: The primary node agent that runs on each node
  • Container Runtime: Docker (with cri-dockerd)
  • Networking:
    • CNI plugins: Container Network Interface plugins
    • Flannel: Network overlay for pod-to-pod communication
    • Canal: Calico for network policy and Flannel

🛠️ Tools

  • kubeadm: Cluster lifecycle management and bootstrapping
  • kubectl (alias: k): Kubernetes cluster management and debugging
  • krew: kubectl plugin manager for extending functionality

🎯 Getting Started

Quick Setup

If you want to quickly set up a working cluster, use the automated script:

/opt/lab/init.sh --remove-taint
Available options
OptionDefaultDescription
--remove-taintfalseRemove the NoSchedule taint that may prevent pods from being scheduled to this node.
--cniflannelNetwork add-on to install. Valid values: none, flannel, canal
--no-load-imagesfalseDo not load the images from local cache.
Important

⚠️ When none is selected as the network addon, the initialization script will skip installing any CNI plugin.

On the dev-machine, run the following command to configure kubectl:

/opt/lab/configure.sh

📚 Learn More

Note

💡 For more information, check out the kubeadm playground.

🧩 Related Content

📖 Tutorials

🧪 Playgrounds

Happy learning! 🚀

Every playground includes

A real VM, not a container

Get root on a VM with its own kernel, so Docker, Kubernetes, and systemd just work.

Read the docs →

SSH from browser or CLI

Use the built-in web terminal, or connect with labctl ssh, plain ssh, scp, or rsync.

Read the docs →

Drive it with AI

Let Claude, Codex, or any MCP client start this playground and run commands in it.

Read the docs →

Expose HTTP(S) ports

Give any web app running inside the VM a public URL - for yourself or to share with others.

Read the docs →

Share terminals

Invite others into your terminal session, or open it yourself from another device.

Read the docs →

Customize with init scripts

Add shell scripts that run at boot to install packages, clone repos, or seed test data.

Read the docs →

Private networking

VMs reach the internet via NAT with no public IP; several VMs share bridge networks.

Read the docs →

Ephemeral or persistent

By default, VMs are destroyed when the session ends; enable persistence to keep the disks for next time.

Read the docs →

Built-in container registry

A private registry.iximiuz.com for every playground to share images across services and VMs.

Read the docs →

Learn more about playgrounds
Start
Settings