No disk left due to buildx state: how to safely clean the leftovers?

[PetitLepton]

Hi,

we are using the buildx GitHub action which, if I understood properly, had a bug related to keeping the state starting from June 16th, bug that should have been fixed in the latest release from yesterday.

Due to the bug, we are currently left on our instance with no disk space left due mostly to the following states taking a huge amount of space. Would you be kind enough to tall me how to clean those states safely?

14G	docker/volumes/buildx_buildkit_builder-a598bbd6-c62b-4a8f-87e0-cceca4a4da900_state
14G	docker/volumes/buildx_buildkit_builder-bf46dc08-a0da-4f40-b563-5bb540514a6e0_state
6.8G	docker/volumes/buildx_buildkit_builder-fddc5e4c-2585-44eb-87de-39c46dfab9020_state

A simple docker build ls is already failing

> docker buildx ls
ERROR: mkdir /home/ec2-user/.docker: no space left on device

Thanks in advance!

[crazy-max]

You can probably remove dangling volumes on this machine with docker volume prune.

[thaJeztah]

curious; do we know why docker buildx ls creates the directory? (should it?)

docker buildx ls
ERROR: mkdir /home/ec2-user/.docker: no space left on device

[crazy-max]

curious; do we know why docker buildx ls creates the directory? (should it?)

I can't find where this directory is created. Only place is when invoking buildx install:

buildx/commands/install.go

Lines 19 to 22 in d09eb75

	dir := config.Dir()
	if err := os.MkdirAll(dir, 0755); err != nil {
	return errors.Wrap(err, "could not create docker config")
	}

@PetitLepton Can you run docker --debug buildx ls and post the output?

[PetitLepton]

Here it is.

NAME/NODE                                       DRIVER/ENDPOINT             STATUS  BUILDKIT PLATFORMS
builder-fddc5e4c-2585-44eb-87de-39c46dfab902 *  docker-container                             
  builder-fddc5e4c-2585-44eb-87de-39c46dfab9020 unix:///var/run/docker.sock running v0.22.0  linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/amd64/v4, linux/386
default                                         docker                                       
  default                                       default                     running v0.12.5  linux/amd64, linux/amd64/v2, linux/amd64/v3, linux/amd64/v4, linux/386

[crazy-max]

@PetitLepton I guess you ran it after volume pruning right? Don't see the error in your output anymore

[PetitLepton]

Yes, my bad sorry. And I can't help you much further right now as there is a power outage here.