Docker vs Podman: source lines of code compared

The Docker vs Podman comparison on OctoCounts shows side-by-side source line counts for moby/moby and podman-container-tools/podman, counted under the rules and on the dates stated below: files, total lines, code lines, comment lines, blank lines, and per-language totals, pinned to the exact commits listed below.

This page compares the source lines of code (SLOC) of moby/moby and podman-container-tools/podman using cached OctoCounts reports. Code size is not code quality: a larger count only means more source material, not a better or worse project.

As of 2026-11-13, moby/moby contains 455,840 total lines (352,369 code) across 2,521 files, while podman-container-tools/podman contains 262,751 total lines (183,586 code) across 1,493 files as of 2026-11-13. moby/moby has about 1.9x the counted code lines of podman-container-tools/podman under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Metricmoby/mobypodman-container-tools/podman
Files2,5211,493
Total lines455,840262,751
Code lines352,369183,586
Comment lines47,39647,855
Blank lines56,07531,310
Languages counted1923

Top languages in moby/moby: Go (90.0% of code), YAML (8.1% of code), Shell (0.7% of code). Top languages in podman-container-tools/podman: Go (93.5% of code), Perl (1.8% of code), PowerShell (1.0% of code). Go, Shell appear in both top language lists; YAML, Dockerfile, BASH appear only in moby/moby's top languages; Perl, PowerShell, C appear only in podman-container-tools/podman's top languages.

Methodology: both counts come from cached OctoCounts reports generated with tokei. moby/moby was counted at ref master (commit 06db1734267b) on 2026-11-13; podman-container-tools/podman was counted at ref main (commit a6a942f2ae0f) on 2026-11-13. See the counting methodology for ignored directories and analysis options.

Both reports use the same engine and effective counting rules. Repository declarations, when enabled, are specific to each repository. moby/moby: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed. podman-container-tools/podman: tokei-15.0.0, policy directories-v1; docs excluded, tests excluded, generated excluded. Excluded directory names: .cache, .generated, .git, .next, __tests__, build, dist, doc, docs, documentation, fixtures, gen, generated, node_modules, target, test, tests, vendor. Ignored languages: none. Repository declarations: off. Exclusions are rule-based; they do not prove that every test, document or generated file was removed.

About this comparison

Background observations recorded on 2026-10-16; language descriptions here are historical context, not claims about the current filtered shares. Use this page's measured language breakdown for current counts. Repository layout before counting filters: moby/moby is the Moby project repository — the upstream open-source components from which the Docker Engine is assembled — rather than the Docker CLI or Desktop products, which live in other repositories. podman-container-tools/podman is the Podman repository: the daemonless container engine and its accompanying tooling. Both are container-engine source trees written largely in Go, counted on the dates shown above.

Both repositories are predominantly Go, and the per-language tables show that on both sides; this page compares two Go codebases in the same product category of container engines.

Podman's repository includes additional command-line and companion components alongside the engine, while Moby's repository is the engine upstream from which Docker's commercial products are built — so each total is organized around a different release boundary.

The left count is Moby, Docker's upstream project, not the Docker product most users install; Docker Desktop and the Docker CLI ship from other repositories, so neither total here is a complete picture of either vendor's product surface.

Sources: moby/moby repository (upstream components of the Docker Engine) · podman-container-tools/podman repository. Statements verified 2026-10-16.

Evidence and next steps:

Saved reports remain subject to cache cleanup and replacement. Export their JSON for durable citation; live report URLs can change.

Note: code size is not code quality. OctoCounts only reports reproducible line counts and makes no claim that either project is better.

Compare FAQ

Which has more lines of code, moby/moby or podman-container-tools/podman?

As of 2026-11-13, moby/moby contains 455,840 total lines (352,369 code) across 2,521 files, while podman-container-tools/podman contains 262,751 total lines (183,586 code) across 1,493 files as of 2026-11-13. moby/moby has about 1.9x the counted code lines of podman-container-tools/podman under the same engine and counting rules. Code size is not code quality: a larger count only means more source material, not a better or worse project.

Does more source lines of code mean more complexity?

Not necessarily. SLOC measures size, not complexity, quality, or maintainability. A larger codebase can mean more features, more generated or vendored code, more verbose language idioms, or more tests — none of which imply the code is harder to work with. Use SLOC to gauge the scale of what you'd be reading or maintaining, not as a quality signal for moby/moby, podman-container-tools/podman, or any repository.

How is this comparison calculated?

Methodology: both counts come from cached OctoCounts reports generated with tokei. moby/moby was counted at ref master (commit 06db1734267b) on 2026-11-13; podman-container-tools/podman was counted at ref main (commit a6a942f2ae0f) on 2026-11-13. See the counting methodology for ignored directories and analysis options.

Can I compare a different branch, tag, or commit?

Yes. This page shows the default branch for each repository. Use the interactive comparison tool to pick any public GitHub repository, branch, tag, or commit SHA for both sides and get a fresh side-by-side report.