-
Notifications
You must be signed in to change notification settings - Fork 819
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
Dangling images left after each run of hack/local-up-karmada.sh #4914
Comments
Hi @B1F030, would you like to contribute a PR? |
I wonder how these dangling images were created. Is there a way to avoid them? |
refer to https://docs.docker.com/config/pruning/
The common ways are:
|
Sure.
These images are generated because every time we run the
Generally, dangling images have lost their value of existence and can be deleted at will. They are generated because:
But on the other hand, keeping dangling images could help to accelerate image building by using cache layer. |
What would you like to be added:
Clean up dangling images after each run of
hack/local-up-karmada.sh
.Why is this needed:
When we use
hack/local-up-karmada.sh
to start a demo environment for more than one times, there will be a lot of dangling images like this:Could be resolved by adding a command in script like this:
docker image prune -f
.The text was updated successfully, but these errors were encountered: