runc configuration on rootless startup
Open
- Dominant language
- C
- Stars
- 4.1k
- Forks
- 444
- Avg merge
- 1d 18h
- Merged PRs (30d)
- 43
Description
I am starting my container by an unprivileged user which has subid, subgid mappings. The user is dynamic. The mappings have to be put on the config.json and I have a script for this which updates the existing config.json file.
What are the thoughts on passing the subuid, subgid mappings to runc dynamically?
Option 1 can be that they are part of the command line argument to the create.
Option 2 can be that they are part of the command line argument to the spec argument. The spec argument already takes 1 option today (--rootless).
Contributor guide
Assessment
This issue has not been assessed yet.