-
Notifications
You must be signed in to change notification settings - Fork 18.6k
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Performing an image build with RUN adduser -u 1000000000 will result in no space left on host #28920
Comments
Confirmed that this is still an issue in master 1ef10c8. reproduction:
|
When I hit the issue, Probably the issue is a bug of the implematation of However, when I ran |
Closing as a dupe of #5419 (comment)
|
As mentioned in #5419 (comment), |
@AkihiroSuda I am not sure how severe this is... although |
Just doing some hacking with info I found on the internet. Built a script that checks for sparse files.
Could we change docker commit to not save sparse files and just zero them out? |
We would need to wait for golang/go#13548 to implement that. |
Last action on that was 9 Months ago. :^( |
@rhatdan seems like someone commented on that pr to get a fix in by go 1.9 (more likely 1.10) |
Let's hope so, as this can cause issues with automated build processes.
|
Description
Doing an
adduser -u 1000000000
in a RUN will cause the filesystem on the host to fill up and report aNo space on device left
.Steps to reproduce the issue:
Dockerfile
withRUN adduser user -u 1000000000 -g 0 -r -m -d /home/user/ -c "Default Application User"
docker build -t test .
no space left on device
is shownDescribe the results you received:
Describe the results you expected:
Succeeding build
Additional information you deem important (e.g. issue happens only occasionally):
Reproduced on GItlab CI runner as https://gitlab.com/gbraad/issue-docker/builds/6767776 (Source Dockerfile can be found in the repo: https://gitlab.com/gbraad/issue-docker)
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
The text was updated successfully, but these errors were encountered: