No space left on device

[ruidc]

... when pulling containers. All drives in windows still have space - what device is running

already tried:

• prune
• image removal
• factory reset
• uninstall + reboot + reinstall

Diagnostic id:

• A9A0EDF3-69CD-4E05-B440-DC6D9080FE46/2017-03-21_18-17-41

[friism]

What image are you pulling and how much space is on your system drive?

[ruidc]

images are from our own registry and have tens of gigabytes free on all drives. From: Michael Friis <notifications@github.com> To: docker/for-win <for-win@noreply.github.com> Cc: ruidc <ruidc@yahoo.com>; Author <author@noreply.github.com> Sent: Wednesday, 22 March 2017, 8:11 Subject: Re: [docker/for-win] No space left on device (#600) What image are you pulling and how much space is on your system drive?— You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[principat]

The problem is that not the free storage of your physical drives is interesting, but the free storage of the vm (initial 60GB).

Start hyper-V Manager, stop docker vm (MobyLinuxVm), increase the size of the virtual hard drive and restart docker. This should help

[aensidhe]

Start hyper-V Manager, stop docker vm (MobyLinuxVm), increase the size of the virtual hard drive and restart docker. This should help

Does not help us.

We have CI and agents are constantly building, pulling and pushing images. Within 2 working days it is guaranteed that we'll have "no space left on device error".

[jasonbivins]

Hi @ruidc @aensidhe
The MobyLinuxVM is hard-coded for a 60gb drive. You can change this by making a change to one of our startup scripts.

1. Stop Docker
2. Go to C:\Program Files\Docker\Docker\resources and find MobyLinux.ps1 line 86
3. Then find $global:VhdSize = 60* 1024* 1024*1024 Change the 60 to the drive size you'd like.
4. Restart Docker

Please keep in mind that this change will be reverted after upgrades or reinstalls.

Please let me know if this helps and I'll put it into a KB

[ruidc]

Sorry but I've gone back to toolbox where at least i have transparency into what is going on. But a KB would have been nice to have sry the time i was taking a decision.  Regards, Rui 

…

-------- Original message -------- From: Jason Bivins <notifications@github.com> Date: 2017/07/28 20:03 (GMT+01:00) To: docker/for-win <for-win@noreply.github.com> Cc: ruidc <ruidc@yahoo.com>, Mention <mention@noreply.github.com> Subject: Re: [docker/for-win] No space left on device (#600) Hi @ruidc @aensidhe The MobyLinuxVM is hard-coded for a 60gb drive. You can change this by making a change to one of our startup scripts. Stop Docker Go to C:\Program Files\Docker\Docker\resources and find MobyLinux.ps1 line 86 Then find $global:VhdSize = 60* 1024* 1024*1024 Change the 60 to the drive size you'd like. Restart Docker Please keep in mind that this change will be reverted after upgrades or reinstalls. Please let me know if this helps and I'll put it into a KB — You are receiving this because you were mentioned. Reply to this email directly, view it on GitHub, or mute the thread. {"api_version":"1.0","publisher":{"api_key":"05dde50f1d1a384dd78767c55493e4bb","name":"GitHub"},"entity":{"external_key":"github/docker/for-win","title":"docker/for-win","subtitle":"GitHub repository","main_image_url":"https://cloud.githubusercontent.com/assets/143418/17495839/a5054eac-5d88-11e6-95fc-7290892c7bb5.png","avatar_image_url":"https://cloud.githubusercontent.com/assets/143418/15842166/7c72db34-2c0b-11e6-9aed-b52498112777.png","action":{"name":"Open in GitHub","url":"https://github.com/docker/for-win"}},"updates":{"snippets":[{"icon":"PERSON","message":"@jasonbivins in #600: Hi @ruidc @aensidhe \r\nThe MobyLinuxVM is hard-coded for a 60gb drive. You can change this by making a change to one of our startup scripts.\r\n1. Stop Docker\r\n2. Go to C:\\Program Files\\Docker\\Docker\\resources and find MobyLinux.ps1 line 86\r\n3. Then find `$global:VhdSize = 60* 1024* 1024*1024` Change the 60 to the drive size you'd like. \r\n4. Restart Docker \r\n\r\nPlease keep in mind that this change will be reverted after upgrades or reinstalls.\r\n\r\nPlease let me know if this helps and I'll put it into a KB"}],"action":{"name":"View Issue","url":"#600 (comment)"}}}

[principat]

Why was it closed without solution just a workaround?

[mriegr]

This problem persisted since 3 years ago without any working solution introduced by the Docker team. Even with 500GB of vm storage this problem keeps occuring in our place.

docker system prune failed to clear data buildup in the vm and just shows Total reclaimed space: 0B everytime.

The only workaround is to recreate the vm by either resetting Docker to factory defaults or increasing the vm storage size.

[docker-robott]

Closed issues are locked after 30 days of inactivity.
This helps our team focus on active issues.

If you have found a problem that seems similar to this, please open a new issue.

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