TechDebt: non-root user does not work with kuryr container
Bug #1594673 reported by
Hui Kang
This bug affects 1 person
| Affects | Status | Importance | Assigned to | Milestone | |
|---|---|---|---|---|---|
| kolla |
Expired
|
Undecided
|
Unassigned | ||
Bug Description
kuryr container requires root user in the container for two reasons
- Kuryr currently requires root privilege to operate [1].
- In addition, not all container drops root, e.g., nova-libvirt [2]. These containers have to operate on some host directory like kuryr.
As things get improved, we need to fix this to enable non-root user in the kuryr container.
[1] https:/
[2] https:/
| Changed in kolla: | |
| assignee: | nobody → Hui Kang (huikang27) |
| importance: | Undecided → High |
| milestone: | none → newton-2 |
| status: | New → Confirmed |
| Changed in kolla: | |
| milestone: | newton-2 → newton-3 |
| Changed in kolla: | |
| milestone: | newton-3 → newton-rc1 |
| Changed in kolla: | |
| milestone: | newton-rc1 → newton-rc2 |
| Changed in kolla: | |
| importance: | High → Medium |
| Changed in kolla: | |
| milestone: | newton-rc2 → ocata-1 |
| Changed in kolla: | |
| milestone: | ocata-1 → ocata-2 |
| Changed in kolla: | |
| milestone: | ocata-2 → ocata-3 |
| Changed in kolla: | |
| milestone: | ocata-3 → ocata-rc1 |
| Changed in kolla: | |
| milestone: | ocata-rc1 → pike-1 |
| Changed in kolla: | |
| milestone: | pike-2 → pike-3 |
| Changed in kolla: | |
| milestone: | pike-3 → pike-rc1 |
| Changed in kolla: | |
| milestone: | pike-rc1 → queens-1 |
| Changed in kolla: | |
| milestone: | queens-2 → queens-3 |
| Changed in kolla: | |
| milestone: | queens-3 → queens-rc1 |
| Changed in kolla: | |
| milestone: | queens-rc1 → queens-rc2 |
| Changed in kolla: | |
| milestone: | queens-rc2 → rocky-1 |
Revision history for this message
| Jeffrey Zhang (jeffrey4l) wrote Cleanup EOL bug report | #1 |
| Changed in kolla: | |
| assignee: | Hui Kang (huikang27) → nobody |
| importance: | Medium → Undecided |
| status: | Confirmed → Expired |
To post a comment you must log in.
This is an automated cleanup. This bug report has been closed because it
is older than 18 months and there is no open code change to fix this.
After this time it is unlikely that the circumstances which lead to
the observed issue can be reproduced.
If you can reproduce the bug, please:
* reopen the bug report (set to status "New")
* AND add the detailed steps to reproduce the issue (if applicable)
* AND leave a comment "CONFIRMED FOR: <RELEASE_NAME>"
Only still supported release names are valid (OCATA, PIKE, QUEENS, ROCKY, ROCKY).
Valid example: CONFIRMED FOR: OCATA