Open dgageot opened 6 years ago
Did you see https://github.com/moby/moby/issues/35071 ? Not sure it helps but looks strange
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
/remove-lifecycle stale
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
This is still happening, any update?
/remove-lifecycle stale
This is still happening to me with Docker Desktop 2.2.0.3, engine 19.03.5
Do you have other steps to reproduce this error ? I couldn't trigger it last time I tried.
more detailed discussion in https://github.com/GoogleContainerTools/distroless/issues/225
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.
On Docker for Mac
18.06.1-ce-mac74 (26766)
docker run --entrypoint=sh --rm gcr.io/distroless/base:debug -c ls
should outputInstead, 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.