Welcome back to another Solo Leveling Log. In the last post, we wrapped up Chapters 1 and 2 of Docker Deep Dive. This time, we’re stepping into Chapter 3, where the focus shifts to getting Docker installed and ready so we can start working with containers.
This chapter lays the foundation for the rest of the book. It covers three main installation methods, and I took the time to try all three. The goal here is to share that experience so following along feels smoother.
Docker Desktop
The book’s first recommendation is Docker Desktop — and for good reason.
It’s a complete package that includes:
- Docker Engine
- Built-in plugins
- A marketplace
- Even a single-node Kubernetes cluster
It’s free for personal use, but organizations need a license. Kubernetes will be explored later in its own segment, so we won’t worry about that yet.
We set up Docker Desktop inside a Windows virtual machine for accessibility. Many people already have Windows systems, which makes this route easy to follow. Everything we do here can also be replicated in Linux — we’ll move to that later.
Before installation, one key thing must be in place: nested virtualization. This allows a virtual machine to run its own virtual machines. Without it, Docker Desktop in a VM won’t function correctly. Once confirmed, we upload a Windows installation ISO to our virtual environment and create a VM with enough CPU, memory, and storage to handle container workloads.
With Windows installed, downloading and installing Docker Desktop is straightforward from the official Docker site. During setup, enabling WSL (Windows Subsystem for Linux) is essential — it provides the Linux compatibility Docker relies on in Windows. Once installed, Docker Desktop offers a clean, user-friendly interface with tabs for containers, images, volumes, and a built-in terminal. For now, we’re keeping it simple and not launching containers yet — that comes in the next chapter.
Multipass
Next up is Multipass, a tool from Canonical that spins up Ubuntu instances in seconds on Windows, Linux, or macOS. It’s perfect for quickly testing Docker in a clean environment without manually creating a full VM.
Installation is quick. On Windows, Hyper-V is the recommended backend, and Multipass adds itself to the system PATH so commands can be run from anywhere. Once installed, launching an Ubuntu instance is as simple as clicking a button or running a command. This instantly provides a Linux shell ready for Docker installation.
While we may not use Multipass heavily in this series, it’s a handy option worth knowing. In a real workflow, it’s a great way to isolate tests or experiment without impacting the main system.
Docker on Linux (and an LXC Twist)
The classic method is installing Docker directly on a Linux server — reliable, and widely used. However, I decided to push things a little further by installing it inside an LXC container.
LXC containers are lightweight, and running Docker inside them isn’t officially recommended, especially in unprivileged mode, due to permission and stability issues. Still, it’s a valuable experiment.
The process is simple:
- Update the container’s packages.
- Install supporting packages for certificates and repository management.
- Add Docker’s GPG key and repository.
- Install Docker and its CLI tools.
Once installed, Docker works, though testing and tweaking permissions will be necessary for certain workloads. If stability becomes a problem, switching to a full VM with a standard Linux distribution is always an option.
Final Thoughts
Those are the three main installation methods outlined in the book:
- Docker Desktop – Beginner-friendly, feature-rich, great for quick starts.
- Multipass – Fast Ubuntu environments for quick testing.
- Docker on Linux – The standard, stable approach (with an optional experimental LXC path).
For the rest of this series, Docker Desktop will be the primary environment since it aligns closely with the book’s examples and provides an approachable learning curve. Multipass and the LXC experiment will remain in our toolkit for testing and exploration.
Our environment is now ready for the next stage. Step by step, we’re building momentum, and the real hands-on work is just getting started. Stay geeking, stay curious —and I’ll see you in the next one.
