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
Improve idmap detection/handling #329
Comments
Quick update that my massive idmap branch addresses everything except the one before last point, working on that one now. |
stgraber
added a commit
to stgraber/incus
that referenced
this issue
Jan 6, 2024
Closes lxc#329 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
stgraber
added a commit
to stgraber/incus
that referenced
this issue
Jan 6, 2024
Closes lxc#329 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Got that one covered now too. |
stgraber
added a commit
to stgraber/incus
that referenced
this issue
Jan 6, 2024
Closes lxc#329 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
stgraber
added a commit
to stgraber/incus
that referenced
this issue
Jan 6, 2024
Closes lxc#329 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
stgraber
added a commit
to stgraber/incus
that referenced
this issue
Jan 6, 2024
Closes lxc#329 Signed-off-by: Stéphane Graber <stgraber@stgraber.org>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Currently if the system isn't correctly configured (/etc/subuid and /etc/subgid), it leads to very confusing errors coming from liblxc. This is all data that Incus already parses on startup, so we should be able to perform a check ourselves and give a better error.
On systems where uidmap is in use (newuidmap/newgidmap available), we need to properly handle:
The text was updated successfully, but these errors were encountered: