My C drive is running out of space (I’m running Windows in Parallels). How can I put my image files onto a network drive.
I’ve read posts about using Hyper-V Manager to move the VM but it seems to be for the Linux containers and I’m interested in the storage location of my windows containers. These seem to be in C:/ProgramData/Docker
. How can I change the location to my Y: network drive?
friism
(Michael Friis)
December 27, 2016, 3:25pm
2
This setting is not available in Docker for Windows yet for Windows containers, but we’re working on it. Alternatively, you can uninstall Docker for Windows and run the Windows daemon manually: https://docs.microsoft.com/en-us/virtualization/windowscontainers/quick-start/quick-start-windows-10
Pass the -g
option when running dockerd --register-service
to specify a different graph driver storage location
jornh
(Jornh)
December 27, 2016, 3:35pm
3
There is already an issue filed with an acknowledged feature request for the Docker for Windows UI here:
opened 03:02PM - 31 Oct 16 UTC
closed 11:53AM - 05 Jan 17 UTC
kind/feature
status/acknowledged
status/4-fix-released-beta
version/18.03.1-ce-win65
version/10.0 14393
lifecycle/locked
moved issue over from [docker/docker #27899](https://github.com/docker/docker/is… sues/27899):
With the new windows containers, I started playing around. The windowsservercore docker image is large and filled up my C: drive completely. (no getting a larger disk is not an option).
Where can I configure Docker to put all the ProgramData\Docker stuff? Can I move the ProgramData\Docker to a different disk?
**Description**
I am experimenting with the docker windows container services and have sucessfully pulled "windowsservercore" and used "chocolatey" do get some stuff installed. Awsome. Works. As I have now learned C:\ProgramData\Docker\... contains all the images\containers\volumes\...
After a few experiments my C: filled up completly. So I decided to move either C:\ProgramData or C:\ProgramData\Docker to another drive. I roughly followed the steps for moving the [C:\Users folder](http://www.tenforums.com/tutorials/1964-users-folder-move-location-windows-10-a.html#MethodTwo) and wanted to used "mklink" to link it back while in Windows "Save Mode".
**Steps to reproduce the issue:**
1. Get a almost full C: Drive
2. Pull large docker image (e.g. windowsservercore) to fill up C: drive
3. wait for explosion - windows is not happy if C: has 0 bytes free ;-)
4. reboot in Safe Mode
5. copy C:\ProgramData\Docker to different disk via "robocopy C:\ProgramData\Docker D:\ProgramData\Docker /MIR /COPYALL"
**Describe the results you received:**
Robocopy failed on so many levels, that I gave up moving it e.g. "bootmgr" could not be accessed... ApplicationData recursion problem (even though I am system in safe mode environment...)
I could not even remove target folder in safe mode, after the robocopy failed...
**Describe the results you expected:**
When installing Docker, I would like to tell it where to put the ProgramData\Docker stuff.
When running Docker, I would like to "move" the ProgramData\Docker stuff to another disk.
**Output of `docker version`:**
```
λ docker version
Client:
Version: 1.12.3
API version: 1.24
Go version: go1.6.3
Git commit: 6b644ec
Built: Thu Oct 27 00:09:21 2016
OS/Arch: windows/amd64
Experimental: true
Server:
Version: 1.12.2-cs2-ws-beta
API version: 1.25
Go version: go1.7.1
Git commit: 050b611
Built: Tue Oct 11 02:35:40 2016
OS/Arch: windows/amd64
```
**Output of `docker info`:**
```
λ docker info
Containers: 0
Running: 0
Paused: 0
Stopped: 0
Images: 1
Server Version: 1.12.2-cs2-ws-beta
Storage Driver: windowsfilter
Windows:
Logging Driver: json-file
Plugins:
Volume: local
Network: nat null overlay
Swarm: inactive
Security Options:
Kernel Version: 10.0 14393 (14393.351.amd64fre.rs1_release_inmarket.161014-1755)
Operating System: Windows 10 Pro
OSType: windows
Architecture: x86_64
CPUs: 8
Total Memory: 11.99 GiB
Name: BLAUBEERE10
ID: ZUJM:NRJZ:TPN2:OCLO:4BSZ:CB2V:HWDZ:LIRK:V7AD:XPZL:IUM6:56CU
Docker Root Dir: C:\ProgramData\Docker
Debug Mode (client): false
Debug Mode (server): false
Registry: https://index.docker.io/v1/
Insecure Registries:
127.0.0.0/8
```
**Additional environment details (AWS, VirtualBox, physical, etc.):**
physical machine
If you follow links and comments in there it looks like the underlying docker daemon already supports moving via e.g. setting "graph": "Y:\\ProgramData\\Docker"
in C:\ProgramData\Docker\config\daemon.json
. Note the info on moving images safely :
If you want to move already downloaded images, the safest option is probably to docker save
them, then change the daemon option, then run docker load
. Or you can just download them anew.
Edit : Duh, looks like @friism beat me to it, probably with a more correct answer
demanp
(Demanp)
December 19, 2017, 10:27am
4
Does this solution works with docker toolbox ?
I can’t find “C:\ProgramData\Docker\config\daemon.json”