Tool

Docker

Containers · Engine + Desktop · docker.com

The common way to package an app with its dependencies and run it the same way on a laptop, a VPS, or a lab box. Useful — and easy to confuse Engine with Desktop.

What it is

Docker Engine (the open-source daemon / CLI lineage, including Moby) runs containers on Linux and is what most server installs mean by “Docker.” Docker Desktop is a separate product: a GUI + VM tooling for Mac/Windows (and a Desktop build on Linux) that bundles Engine-like pieces under Docker’s subscription terms.

People say “Docker” for both. Licenses and who must pay are not the same.

What it replaces

It replaces “install the runtime, the libs, and hope the host matches prod” with an image you can ship and run elsewhere. For AI/self-hosting stacks it replaces hand-rolled process supervisors for apps that already ship as images (Open WebUI, Nginx Proxy Manager, databases).

It does not replace thinking about volumes, networking, updates, or backups. A container that loses its data directory is still lost data. And Desktop is not required just because you want containers on a Linux server — Engine alone is enough there.

License

Docker’s open-source components (including Engine / Moby) are generally under the Apache License 2.0. Commercial use of Engine itself under those terms is the open-source story.

Docker Desktop is licensed under the Docker Subscription Service Agreement. Per Docker’s docs: Desktop is free for personal use, education, non-commercial open source, and small businesses (fewer than 250 employees and under $10M annual revenue). Larger commercial use needs a paid Docker subscription. Docker states that Engine’s open-source licensing is separate from Desktop’s subscription rules — do not treat “I run containers” as “Desktop is free for my company.”

Where it falls over

• Desktop vs Engine confusion gets people into compliance arguments they did not expect.
• Bind mounts, permissions, and “works on my Mac” networking still bite; GPU passthrough is another footgun.
• Images rot. Unpinned :latest tags and forgotten base CVEs are how quiet boxes get loud.
• Rootful defaults and exposed Docker sockets are a privilege escalation story if you treat the daemon like a toy.
• Orchestration (Swarm/K8s) is a different job than “one compose file on a VPS.”

Who it's for

Anyone packaging or running self-hosted services with repeatable images. Solo and small teams on Engine; orgs that need Desktop should read the subscription page before assuming free.

← Tools · Home · docker.com