Repository navigation
feat(compose): hardlink store blobs into containerd - #148
Merged
Merged
Conversation
mike-sul
force-pushed
the
feat/containerd-install-linkin
branch
2 times, most recently
from
October 21, 2026 14:47
97821e9 to
0a4ae6e
Compare
mike-sul
changed the title
mike-sul
force-pushed
the
feat/containerd-install
branch
from
October 22, 2026 10:06
954e58a to
7dbb13b
Compare
mike-sul
force-pushed
the
feat/containerd-install-linkin
branch
2 times, most recently
from
October 22, 2026 10:33
53034df to
f2f8ccf
Compare
mike-sul
force-pushed
the
feat/containerd-install
branch
from
October 22, 2026 10:33
7dbb13b to
2cc3bb7
Compare
mike-sul
force-pushed
the
feat/containerd-install-linkin
branch
from
October 22, 2026 10:40
f2f8ccf to
e5d5677
Compare
mike-sul
force-pushed
the
feat/containerd-install-linkin
branch
from
October 22, 2026 10:56
e5d5677 to
04de0df
Compare
The containerd install copied every compressed layer from the store into containerd's content store before unpacking it, a transient second copy that doubled the bytes written by an install. The note says how a layer is checked, hardlinked and registered with no bytes copied, and that the store and the content store must be on one filesystem. Assisted-by: Claude Code:claude-fable-5-1 Signed-off-by: Mike Sul <mike.sul@foundries.io>
The containerd install copied every compressed layer from the store into containerd's content store before unpacking it: a transient second copy that doubled the bytes written by an install and made its peak space the compressed size of the app. The layer's store blob is now checked for presence and size and hardlinked to the path the content store keeps it at. With the default "shared" content policy containerd registers a file already at that path without copying or hashing it, so the existing WriteBlob moves no bytes; the blob was verified at pull and the unpack checks every extracted layer against the image's diff IDs. The store and the content store must be on one filesystem: a link that cannot be made fails the install, naming both. The test environment moves its store onto the test dockerd's data volume for that. Assisted-by: Claude Code:claude-fable-5-1 Signed-off-by: Mike Sul <mike.sul@foundries.io>
mike-sul
force-pushed
the
feat/containerd-install-linkin
branch
from
October 22, 2026 11:09
04de0df to
d287b1d
Compare
mike-sul
marked this pull request as ready for review
October 22, 2026 11:22
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
The containerd install copied every compressed layer from composectl's store into containerd's content store before unpacking it: a transient second copy that doubled the bytes written per install and made its peak space the compressed size of the app.
The layer is now verified against its digest and hardlinked to the path the content store keeps it at; with containerd's default shared content policy the registration that follows moves no bytes. The store and the content store must therefore be on one filesystem: a link across filesystems fails the install naming both paths. The test environment moves its store onto the test dockerd's data volume for that.
Based on #147. Test:
TestCtrdInstallLinksLayers,TestCtrdInstallFailsAcrossFilesystemsandTestCtrdLinkedBlobAndGCin the e2e suite withCONTAINERD_SNAPSHOTTER=true. Design note:docs/containerd-install-linkin-progress-plan-2026-10-19.md.