Feature add VTPM support for runc container
Nobody has claimed this yet.
Assessment
- Difficulty
- 5/5
- Estimated time
- Over a week
- Newbie friendliness
- 25/100
- Issue type
- Feature
- Clarity
- Mostly clear
- Activity status
- Stale
- Tech stack
- go
- Domain
- devops, operating-systems, security
Research direction
Start by reviewing the linked vTPM configuration proposals for runc and runtime-spec, then inspect the external swtpm_cuse and go-tpm bug reports listed in the checklist. The work is complete when those prerequisites are resolved and runc can bind the vTPM device lifecycle to container creation under the stated root, AppArmor, and cgroup constraints.
Written by the indexing model from the issue text.
Description
This issue is to bind the creation of virtual TPM devices with container creation. The virtual TPM devices can be used to perform attestation (e.g using the Direct Anonymous Attestation protocol).
The virtual TPM devices are simulated by swtpm_cuse binary (vTPM device is created by CUSE) and independent from a container namespace.
The initial state of vTPM device can be prepopulated by swtpm_setup binary (e.g create EK key pair, EK + platform certs).
After the vTPM devices are created, the /dev/tpm + vTPMName will be passed to the container. In order to pass different vTPM devices with the same container path to the different containers, the initial device host path is generated.
This feature requires root rights so it can not be performed with rootless containers. However, the generated device host path can be passed to the unshared user namespace with mapped root user.
Because the swtpm_cuse binary is running always with the life a container, then it is restricted by apparmor profile.
Also, there is a restriction to run runc in a container because all vTPM device major and minor should be predefined (and they should be passed to the container cgroup device allow list).
The steps to implement before merging the feature:
- Dominant language
- Go
- Stars
- 13.5k
- Forks
- 2.3k
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 30
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
More from opencontainers/runc
-
`root.readonly` is silently ignored (rootfs left writable) when the container has no mount namespace Openllm-generated
Difficulty 2/5 1-3 hours Newbie friendliness 78/100
opencontainers/runc#5371 ·
-
llm-generated
Difficulty 2/5 1-3 hours Newbie friendliness 90/100
opencontainers/runc#5370 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 68/100
opencontainers/runc#2214 · 3 comments ·
-
Difficulty 1/5 Under an hour Newbie friendliness 68/100
opencontainers/runc#1679 · 1 comment ·
-
Difficulty 3/5 1-2 days Newbie friendliness 68/100
opencontainers/runc#5474 ·
All issues in opencontainers/runc
Similar issues
-
optimization optimization:agents-md-curator
Difficulty 2/5 1-3 hours Newbie friendliness 86/100
githubnext/gh-aw-cao#13143 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
blinklabs-io/bursa#904 ·
-
Difficulty 2/5 1-3 hours Newbie friendliness 84/100
yanet-platform/ipfw-go#129 ·
-
bug confmap/provider/googlesecretmanagerprovider needs triage
Difficulty 2/5 1-3 hours Newbie friendliness 72/100
open-telemetry/opentelemetry-collector-contrib#51273 · 2 comments ·
-
bug: AI Gateway client filter lists "Unknown" twice when NULL and literal Unknown clients coexist Openbug
Difficulty 2/5 1-3 hours Newbie friendliness 90/100