Repository navigation
Container: Add the containerd shim - #1822
Draft
Sangho Lee (sangho2) wants to merge 10 commits into
Draft
Sangho Lee (sangho2) wants to merge 10 commits into
Sangho Lee (sangho2) wants to merge 10 commits into
Conversation
added 10 commits
November 7, 2026 03:04
|
ℹ️ Note: This semver check was run against the 🤖 SemverChecks 🤖 Click for details |
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.
This PR adds the containerd shim that runs each container in a LiteBox sandbox. The shim builds the guest's file system from the container's image and read-only mounts, starts the userland broker with the guest service (#1813) as its first process, and drives the service over the broker's hybrid vsock using the guest service protocol (#1809). It works with ctr and nerdctl on rootful and rootless containerd. Note that it only supports read-only mounts for now due to security concerns (thus doesn't work with Kubernetes).