First steps.
WHAT TO INSTALL
The engine on a Linux server, or the desktop application elsewhere.
WHAT THE DESKTOP APPLICATION INCLUDES
A virtual machine running Linux, plus tooling.
WHY THAT MATTERS
Performance and file-sharing behaviour differ from a Linux host.
WHAT TO CHECK AFTER INSTALLING
That the service is running That you can run a simple image
WHAT THE FIRST COMMAND SHOULD BE
Running a small test image, which pulls and executes it.
WHAT HAPPENS ON THAT FIRST RUN
The image is downloaded, then started.
WHAT THE ESSENTIAL COMMANDS ARE
Run a container List running containers List all containers, including stopped List images View logs Execute a command inside a running container Stop and remove
WHAT TO LEARN EARLY
That stopped containers persist until removed.
WHY THAT MATTERS
They accumulate and consume disk.
WHAT TO ADD WHEN EXPERIMENTING
The flag removing the container when it exits.
WHAT TO AVOID ON A SHARED SERVER
Adding users to the group that grants engine access.
WHY
It is equivalent to root, because a container can mount the host filesystem.
WHAT TO PREFER
Rootless operation, or restricted access through sudo.
