fakeroot with ID count < 65536
11 views
Skip to first unread message
Thomas Hartmann
Apr 12, 2021, 6:57:11 AM4/12/21
to singu...@lbl.gov
Hi all,
is there a possibility/switch to use fakeroot for non-user builds with a
ID width less than 65536?
Thing is, that we would like to make it available to our users, but want
to maintain a consistent ID space over our clusters as well as in our
campus user namespace.
Thus we reserved a (upper) range in our user/group IDs for mappings -
but we would use it up pretty fast, if we would assign all our
interested users a full set of 65536 IDs each.
Cheers,
Thomas
is there a possibility/switch to use fakeroot for non-user builds with a
ID width less than 65536?
Thing is, that we would like to make it available to our users, but want
to maintain a consistent ID space over our clusters as well as in our
campus user namespace.
Thus we reserved a (upper) range in our user/group IDs for mappings -
but we would use it up pretty fast, if we would assign all our
interested users a full set of 65536 IDs each.
Cheers,
Thomas
Dave Dykstra
Apr 12, 2021, 5:36:45 PM4/12/21
to singu...@lbl.gov
Hi Thomas,
I'm pretty sure as currently implemented, singularity only supports
65536 user ids per fakeroot user. It would require a feature change
including a configuration option to change that.
Dave
> --
> You received this message because you are subscribed to the Google Groups "singularity" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to singularity...@lbl.gov.
> To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/singularity/d23afd88-741a-ee6f-26ed-33c131653321%40desy.de.
I'm pretty sure as currently implemented, singularity only supports
65536 user ids per fakeroot user. It would require a feature change
including a configuration option to change that.
Dave
> You received this message because you are subscribed to the Google Groups "singularity" group.
> To unsubscribe from this group and stop receiving emails from it, send an email to singularity...@lbl.gov.
> To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/singularity/d23afd88-741a-ee6f-26ed-33c131653321%40desy.de.
Thomas Hartmann
Apr 13, 2021, 3:44:59 AM4/13/21
to singu...@lbl.gov
Hi Dave,
hmmm, OK - I guess we cannot prepare fakeroot then since we might run
out of map'able IDs pretty fast (it has been a bit of a struggle to
allocate an ID range within our UIDs/policies).
In the end, my plan is to avoid clashes between our 'official' proper
campus UIDs and any locally mapped ones - by reserving a section of IDs
for such a somewhat dynamic mapping.
Cheers,
Thomas
hmmm, OK - I guess we cannot prepare fakeroot then since we might run
out of map'able IDs pretty fast (it has been a bit of a struggle to
allocate an ID range within our UIDs/policies).
In the end, my plan is to avoid clashes between our 'official' proper
campus UIDs and any locally mapped ones - by reserving a section of IDs
for such a somewhat dynamic mapping.
Cheers,
Thomas
Dave Dykstra
Apr 13, 2021, 11:47:31 AM4/13/21
to singu...@lbl.gov
I suggest making a github issue on it. I didn't find any previous
issue. I can see why when singularity creates the /etc/sub[ug]id
mappings it would be difficult to deal with different ranges, but I
don't see why it can't allow smaller ranges if something else creates
the mappings. I said below it would require a configuration option but
I don't see why that should even be necessary.
Dave
> To view this discussion on the web visit https://groups.google.com/a/lbl.gov/d/msgid/singularity/16288a71-5692-d91f-ae32-081ef6fdf9bc%40desy.de.
issue. I can see why when singularity creates the /etc/sub[ug]id
mappings it would be difficult to deal with different ranges, but I
don't see why it can't allow smaller ranges if something else creates
the mappings. I said below it would require a configuration option but
I don't see why that should even be necessary.
Dave
Reply all
Reply to author
Forward
0 new messages