buildx Docker volume | root cause and resolution

[scriptPilot]

Dokploy is great and is running fine. I have several applications, build with Railpack or Nixpacks, and two Compose setups with PHP and MariaDB. Now, there is a really huge Docker volume created buildx_buildkit_builder-containerd0_state with around 8GB+ of size ... increasing. Is Dokploy creating this volume? Railpack? Nixpacks? Is there any way to prevent or reduce this volume size? Thanks for your ideas.

[scriptPilot]

Apparently it is triggered / used by Dokploy directly. When I use this cleanup function, the size persists with 8GB+.

[izniburak]

I have similar issue. Probably it's related with the Railpack/Nixpack deployment. Even though I deleted the projects I created with railpack, nixpack or docker compose, the buildx_buildkit_* volume didn't decrease.

[djsisson]

can you try running docker buildx --builder builder-containerd prune see if that helps

since dokploy doesn't use the default builder

[izniburak]

Doesn't work... I got this error: ERROR: no builder "buildx_buildkit_builder-containerd0" found. I tried a few different option for the builder name, but not working.

Also, even if I tried docker system prune -a --volumes -f or docker buildx prune --all -f, I couldn't get any result...

[djsisson]

Can you run docker buildx ls

[djsisson]

I'm assuming the buildx container is not running, gets removed, so you can't run buildx --builder name prune but the volume it uses doesn't get pruned.

So I assume you can recreate the docker buildx container using docker buildx create ... Then prune or just rm the volume directly.

[nareach]

I also have this issue

[nareach]

Sorry for late reply, above is deployment log

[djsisson]

hmm, pretty much everything apart from the build itself was cached, although it doesn't look like it mounts the .next/cache for build, but that still wouldn't be 2GB

just try use the standard nextjs dockerfile and compare (just update the node version, and make sure you're using standalone in next config)

https://github.com/vercel/next.js/blob/canary/examples/with-docker/Dockerfile

[djsisson]

Also can you run

docker buildx --builder default inspect
docker buildx --builder builder-containerd inspect

[nareach]

This is what i received

docker buildx --builder default inspect
Name: default
Driver: docker

Nodes:
Name: default
Endpoint: default
Status: running
BuildKit version: v0.23.1
Platforms: linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/amd64/v4, linux/386
Labels:
org.mobyproject.buildkit.worker.moby.host-gateway-ip: 172.17.0.1
GC Policy rule#0:
All: false
Filters: type==source.local,type==exec.cachemount,type==source.git.checkout
Keep Duration: 48h0m0s
Max Used Space: 1.287GiB
GC Policy rule#1:
All: false
Keep Duration: 1440h0m0s
Reserved Space: 9.313GiB
Max Used Space: 1.863GiB
Min Free Space: 4.657GiB
GC Policy rule#2:
All: false
Reserved Space: 9.313GiB
Max Used Space: 1.863GiB
Min Free Space: 4.657GiB
GC Policy rule#3:
All: true
Reserved Space: 9.313GiB
Max Used Space: 1.863GiB
Min Free Space: 4.657GiB

[djsisson]

That's the default, what about the container version which uses the volume.

The only other suggestion is to create your own builder with the same name that dokploy uses much set much more aggressive gc limits or set the config toml I mentioned in first reply