ls: can't open '.': Value too large for defined data type

[dgageot]

On Docker for Mac 18.06.1-ce-mac74 (26766)

docker run --entrypoint=sh --rm gcr.io/distroless/base:debug -c ls should output

busybox
dev
etc
home
lib
lib64
proc
sys
tmp
usr
var

Instead, it sometimes prints ls: can't open '.': Value too large for defined data type.

It's really sometimes, not always. Sometimes it works just after I restart Docker but if I remove all the images and try again, if ** sometimes* fails.

$ docker version
Client:
 Version:           18.06.1-ce
 API version:       1.38
 Go version:        go1.10.3
 Git commit:        e68fc7a
 Built:             Tue Aug 21 17:21:31 2018
 OS/Arch:           darwin/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.1-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       e68fc7a
  Built:            Tue Aug 21 17:29:02 2018
  OS/Arch:          linux/amd64
  Experimental:     true

[guillaumerose]

Did you see moby/moby#35071 ? Not sure it helps but looks strange

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[nfrankel]

/remove-lifecycle stale

[docker-robott]

Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale comment.
Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows.
/lifecycle stale

[BlueHotDog]

This is still happening, any update?

[mineo]

/remove-lifecycle stale

[silverhammermba]

This is still happening to me with Docker Desktop 2.2.0.3, engine 19.03.5

[guillaumerose]

Do you have other steps to reproduce this error ? I couldn't trigger it last time I tried.

[thaJeztah]

more detailed discussion in GoogleContainerTools/distroless#225

[silverhammermba]

I'm not seeing the issue with that repo. It's unfortunately a proprietary application, but I'm using Docker for Mac to cross build a lot of C++ code and this error occurs during the linking stage.

It does not occur when building with docker e.g. on a linux host.