On Mon, 21 Sep 2020 at 13:48, <ano...@users.sourceforge.net> wrote: > On Sun, Sep 20, 2020 at 09:58:45AM +0700, El boulangero wrote: > > Do you know what's special with the `tianon/true` image? On what OS/release > > is it based? > > It's an image that contains only a single binary that returns 0. That > binary uses no libraries, not even libc. > > It's intended as an extremely light-weight image for purposes that don't > need a whole OS. See, for example, > https://stackoverflow.com/questions/37120260/configure-docker-compose-override-to-ignore-hide-some-containers > > It seems that something changed between 19.03.12+dfsg1-3 and > 19.03.12+dfsg1-4 that is somehow or other assuming the container > contains more infrastructure. If you determine that the bug is upstream, > feel free to forward it to them (and, ideally, revert whatever patch was > added to 19.03.12+dfsg1-4 that caused the problem in the mean time to > avoid breaking other software on the system).
I don't think this is an upstream bug -- I'm using their "docker-ce" package (version "5:19.03.12~3-0~debian-buster") on a host I've got, and here's the result of some tests there: $ docker run --rm tianon/true && echo ok ok $ docker run --rm --user 0:0 tianon/true && echo ok ok $ docker run --rm --user 1000:1000 tianon/true && echo ok ok ♥, - Tianon 4096R / B42F 6819 007F 00F8 8E36 4FD4 036A 9C25 BF35 7DD4
