rimelek
April 27, 2025, 8:41pm
2
Definitely not normal behavior and you could report it as a bug, but the distribution you are using is not supported officially. I understand that Linux Mint is baded on Ubuntu, but Ubuntu is also based on Debian and both has separate installation instructions.
If you can try Docker Desktop on any supported distribution and still experience the same issue, you could report it on GitHub, which you did
opened 11:15AM - 26 Apr 25 UTC
needs-triage
### Description
I am having an issue where a fresh Docker Desktop installs fill… s `~/.docker/desktop/vms/0/data/Docker.raw` with an incredibly large amout of data - over 100 GB, and completely eats up all of my disk space.
### Reproduce
+ Set up Docker’s apt repository:
```
# Add Docker's official GPG key:
sudo apt-get update
sudo apt-get install ca-certificates curl
sudo install -m 0755 -d /etc/apt/keyrings
sudo curl -fsSL https://download.docker.com/linux/ubuntu/gpg -o /etc/apt/keyrings/docker.asc
sudo chmod a+r /etc/apt/keyrings/docker.asc
# Add the repository to Apt sources:
echo \
"deb [arch=$(dpkg --print-architecture) signed-by=/etc/apt/keyrings/docker.asc] https://download.docker.com/linux/ubuntu \
$(. /etc/os-release && echo "${UBUNTU_CODENAME:-$VERSION_CODENAME}") stable" | \
sudo tee /etc/apt/sources.list.d/docker.list > /dev/null
sudo apt-get update
```
+ Download the [DEB package](https://desktop.docker.com/linux/main/amd64/docker-desktop-amd64.deb?utm_source=docker&utm_medium=webreferral&utm_campaign=docs-driven-download-linux-amd64)
+ Install the package using apt:
```
sudo apt-get update
sudo apt-get install ./docker-desktop-amd64.deb
```
+ Start the installed Docker Desktop desktop entry
+ Agree to the Subscription Service
From this moment, my hard drive would start to fill up like crazy.
Running baobab reveals the culprit to be the `~/.docker` directory, specifically the `~/.docker/desktop/vms/0/data/Docker.raw` file.
The only way to stop it is to kill the `com.docker.back` process.
I’ved tried to uninstall and reinstall multiple times (including uninstalling any old packages) yet the issue still persists.
### Expected behavior
`~/.docker/desktop/vms/0/data/Docker.raw` continously grows in size.
### docker version
```bash
Client: Docker Engine - Community
Version: 28.1.1
API version: 1.49
Go version: go1.23.8
Git commit: 4eba377
Built: Fri Apr 18 09:52:14 2025
OS/Arch: linux/amd64
Context: default
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
```
### docker info
```bash
Client: Docker Engine - Community
Version: 28.1.1
Context: default
Debug Mode: false
Plugins:
ai: Docker AI Agent - Ask Gordon (Docker Inc.)
Version: v1.1.3
Path: /usr/lib/docker/cli-plugins/docker-ai
buildx: Docker Buildx (Docker Inc.)
Version: v0.22.0-desktop.1
Path: /usr/lib/docker/cli-plugins/docker-buildx
cloud: Docker Cloud (Docker Inc.)
Version: 0.2.20
Path: /usr/lib/docker/cli-plugins/docker-cloud
compose: Docker Compose (Docker Inc.)
Version: v2.34.0-desktop.1
Path: /usr/lib/docker/cli-plugins/docker-compose
debug: Get a shell into any image or container (Docker Inc.)
Version: 0.0.38
Path: /usr/lib/docker/cli-plugins/docker-debug
desktop: Docker Desktop commands (Beta) (Docker Inc.)
Version: v0.1.6
Path: /usr/lib/docker/cli-plugins/docker-desktop
dev: Docker Dev Environments (Docker Inc.)
Version: v0.1.2
Path: /usr/lib/docker/cli-plugins/docker-dev
extension: Manages Docker extensions (Docker Inc.)
Version: v0.2.27
Path: /usr/lib/docker/cli-plugins/docker-extension
init: Creates Docker-related starter files for your project (Docker Inc.)
Version: v1.4.0
Path: /usr/lib/docker/cli-plugins/docker-init
sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.)
Version: 0.6.0
Path: /usr/lib/docker/cli-plugins/docker-sbom
scout: Docker Scout (Docker Inc.)
Version: v1.17.0
Path: /usr/lib/docker/cli-plugins/docker-scout
Server:
Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?
```
### Diagnostics ID
E249B466-2780-40FB-A4DE-88D0405695AE/20250426111332
### Additional Info
_No response_
But you left out that it was installed on Linux Mint.
We also had a similar report recently
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…
also on Linux Mint