Hello,
Installing from debian package (after fulfilling all prerequisites) on Linux Mint 22, launching Docker Desktop shows “Starting the Docker Engine…”. I noticed the first couple go-arounds that something was eating my free space, up until all 600GB+ of free space had all been used up. The culprit is /.docker/desktop/vms/0/data/Docker.raw which, when trying to start the engine, just grows ad infinitum until i run out of space.
Can’t access any settings within the Docker Desktop GUI since all settings are grayed out while the docker engine is starting. There doesn’t appear to be any way to cancel the initialization without quitting Docker Desktop entirely.
Trying my third clean install of Docker Desktop, and i’m watching it grow in size as we speak. It is currently at 136GB.
Immediately after posting this, I decided to delete the file as it was growing to hopefully get an error out of Docker Desktop, which I did get:
running engine: waiting for the VM setup to be ready: preparing VM: ensuring disk: Cannot resize "/home/headache/.docker/desktop/vms/0/data/Docker.raw" to 146000MiB: truncate /home/headache/.docker/desktop/vms/0/data/Docker.raw: no such file or directory
This is similar to the error i got when i actually ran out of disk space - the error “Cannot resize” was the same but the error was that there was no disk space.
Interesting that it is trying to truncate and it just keeps growing?
Welp, when i deleted the file and got the error message i was able to continue using Docker Desktop and adjust resources settings down from 1TB of disk usage. All seems fine now. Wish resource allocation was presented to the user before initialization started.
Anything that runs in the virtual machine and saves data can increase the size of the virtual disk image. If you could never start Docker Desktop with the engine running, I guess it constantly saved error logs.
An image cannot be truncated when the data in it needs more space than the new requested size.
Still, the behavior is strange as even error logs should not take gigabytes so quickly, so I’m not sure what happened.
Does it look like it works properly now without the image file growing quickly?
Replying from Mobile so, sorry for formatting faux pas.
The issue was nothing more than the alotted disk usage. It defaulted to 1TB which was actually the size of the drive itself, so of course it could never achieve that. No settings were presented before launching that afforded a way to set or change this, nor could I even see this setting while the engine was initiating. I had to force the launch into error by deleting the image file while it was being created, so that I could then adjust the settings and reduce the image size. There seemed to be no other way to “cancel” the initiation. Janky.