fakeroot complains about range count difference

146 views
Skip to first unread message

Thomas Hartmann

unread,
Sep 13, 2019, 4:28:49 AM9/13/19
to singu...@lbl.gov
Hi all,

with Singularity 3.3.0 I am just running into trouble with fakeroot when
I extended the sub-IDs to higher/wider ranges [1].

I.e., I created mapping ranges [2] for my user a range as well as for my
dockerd user [3]. With my intended range being 1M+0.1M > 65536, it
should be sufficiently large, or?

Cheers,
Thomas



[1]
> singularity build --fakeroot --sandbox test.d Singularity
FATAL: could not use fakeroot: entry for user myuser found in
/etc/subuid at line 1 but all with a range count different from 65536

[2]
/etc/sub{uid,gid}
myuser:1000000:100000
dockeruser:1200000:100000


[3]
/etc/docker/daemon.json
{
"userns-remap": "dockeruser"
}


Cedric Clerget

unread,
Sep 16, 2019, 10:51:51 AM9/16/19
to singularity, thomas....@desy.de
Hi Thomas,

Singularity take only entries with a range count of 65536 (last field), it should work if you write this line in /etc/sub{uid,gid}:
myuser:1000000:65536

Cédric

Thomas Hartmann

unread,
Sep 17, 2019, 8:11:15 AM9/17/19
to Cedric Clerget, singularity
Hi Cedric,

it works with
myuser:1000000:65536

Is there a reason, why it has to be exactly 65536 and not ~10k or ~1M?

Cheers and thanks,
Thomas
Reply all
Reply to author
Forward
0 new messages