Skip to content

static: Don't ship READMEs in static archives#463

Open
vvoland wants to merge 1 commit into
docker:mainfrom
vvoland:drop-readme
Open

static: Don't ship READMEs in static archives#463
vvoland wants to merge 1 commit into
docker:mainfrom
vvoland:drop-readme

Conversation

@vvoland

@vvoland vvoland commented Jun 30, 2026

Copy link
Copy Markdown
Collaborator

Remove README.md from the files copied into static tarballs/zips across all packages. LICENSEs are kept; READMEs add no value to a binary release archive and just inflate the output.

For containerd, also drop the component-scoped runhcs.README.md and runc.README.md that were copied alongside the main project README.

READMEs copied into the archives are the upstream GitHub repository
READMEs. They add no value as they mostly describe the project for contributors browsing source and
not users consuming a binary release.

LICENSE files are kept.

Signed-off-by: Paweł Gronowski <pawel.gronowski@docker.com>
@thaJeztah

Copy link
Copy Markdown
Member

We need to review each of these, because I think the README was added for similar reasons that go mod (vendor) includes it; often the LICENSE itself is not applying the license (only a "convenience"), and the README, NOTICE (and sometimes PATENTS) files may contain legal information on the license.

eg; https://github.com/docker/cli/tree/v29.6.1#legal

I think for that one it's mostly redundant / duplicate, but for example this one adds another license (for docs); https://github.com/distribution/distribution/tree/v3.1.1#licenses

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants