I think we have that fix in liblxc 2.0.9 which still needs SRUing to the
various Ubuntu stable releases.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692111
Title:
Unable to configure raw.id_map w
Is there any chance this can get backported to Xenial? I can see this
fix was included in 2.1.0-0ubuntu1, but the LTS package is still at
2.0.8-0ubuntu1~16.04.2.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.ne
** Changed in: lxc (Ubuntu)
Status: Fix Committed => Fix Released
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692111
Title:
Unable to configure raw.id_map with multiple entries
To manage
Marking the LXD side invalid as this will be sorted out by a liblxc
change.
** Changed in: lxd (Ubuntu)
Status: Fix Committed => Invalid
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692111
T
** Changed in: lxd (Ubuntu)
Status: In Progress => Fix Committed
** Also affects: lxc (Ubuntu)
Importance: Undecided
Status: New
** Changed in: lxc (Ubuntu)
Status: New => Fix Committed
** Changed in: lxc (Ubuntu)
Assignee: (unassigned) => Christian Brauner (cbrauner
However, we need to thoroughly review that.
--
You received this bug notification because you are a member of Ubuntu
Bugs, which is subscribed to Ubuntu.
https://bugs.launchpad.net/bugs/1692111
Title:
Unable to configure raw.id_map with multiple entries
To manage notifications about this bug
I've got a patch that should improve things so that you can really use five
mappings:
https://github.com/lxc/lxc/issues/1598
** Bug watch added: LXC bug tracker #1598
https://github.com/lxc/lxc/issues/1598
--
You received this bug notification because you are a member of Ubuntu
Bugs, which i
So I think we might be able to handle this smarter so that users can actually
use the full 5 id map ranges. In order to correctly operate on files on the
host that we want to chown to the container root user we need only two mappings.
So let's say you want to chown a file to belong to 1000:165536
This is an interesting problem. So there are two strategies:
- When LXC adds an additional {G,U}ID mapping we could check whether this would
lead to more than 5 mappings being requested. And while I sympathize with that
I also dislike the fact that the in-kernel limit is arbitrary and I'm not su
So the reason why this happens is that internally the id mapping you
requested will look like this:
NSID HOSTID RANGE
0100 999
999 999 1
1000 1001000 1
1001 10011
1002 1001002 98998
However, the mappings don't include a mapping for UID 0 with which LXD
sets up the container.
10 matches
Mail list logo
