New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
build-next: failed to prune build cache #40480
Labels
Comments
docker daemon logs here.
|
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Description
To debug #40398 issue. I update to nightly version. (I built it myself, because the official nightly channel has stopped updating.)
I want to check if #40398 be related to too many local files, so I run
docker system prune
command.Steps to reproduce the issue:
issue happens only occasionally.
Describe the results you received:
When I executed the
docker system prune --volumes
command, I encountered afailed to prune build cache: failed to remove sha256:4ea5f8c9bd43a7e230f8090740fee2fd9ea04ce8fe 3ca5022a10c40c8648686c: lease "sha256:4ea5f8c9bd43a7e230f8090740fee2fd9ea04ce8fe3ca5022a10c40c8648686c": not found
error.But when I ran this command again, the error disappeared.
Then I tried to find the
sha256:4ea5f8c9bd43a7e230f8090740fee2fd9ea04ce8fe3ca5022a10c40c8648686c
in the error, and I found it!Describe the results you expected:
I want to execute
docker system prune --volumes
normally without encountering errors.Additional information you deem important (e.g. issue happens only occasionally):
yes, issue happens only occasionally.
Output of
docker version
:Output of
docker info
:Additional environment details (AWS, VirtualBox, physical, etc.):
my laptop.
The text was updated successfully, but these errors were encountered: