Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

host-ctr: specify non-colliding runc root #1359

Merged
merged 1 commit into from
Mar 1, 2021

Conversation

samuelkarp
Copy link
Contributor

Description of changes:
The runc root directory is used for storing state needed by the runtime shim. By default, this is /run/containerd/runc. Since we configure host containers to use /run/host-containerd instead of /run/containerd, this change allows all host container state to be inside /run/host-containerd.

Testing done:
Built an aws-ecs-1 AMI and launched it. Verified that the host containers (both control and admin) now had their state.json files stored in /run/host-containerd/runc/default/{admin,control}. Verified that I could run containers manually with ctr and their state was kept in /run/containerd/runc/default/$id. Verified that I could run containers manually with Docker and that their files were unaffected at /run/docker/runtime-runc/moby.

Terms of contribution:

By submitting this pull request, I agree that this contribution is dual-licensed under the terms of both the Apache License, version 2.0, and the MIT license.

The runc root directory is used for storing state needed by the runtime
shim.  By default, this is /run/containerd/runc.  Since we configure
host containers to use /run/host-containerd instead of /run/containerd,
this change allows all host container state to be inside
/run/host-containerd.
@samuelkarp samuelkarp merged commit 4c8ae72 into bottlerocket-os:develop Mar 1, 2021
@samuelkarp samuelkarp deleted the host-ctr-runc-root branch March 1, 2021 17:40
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

5 participants