'minikube image load -' leaves behind a poorly-named /tmp/build.NNNN.tar #18758
Labels
area/image
Issues/PRs related to the minikube image subcommand
kind/improvement
Categorizes issue or PR as related to improving upon a current feature.
What Happened?
minikube image load -
ends up storing a file in /tmp rather than in memory, and does not clean up that temporary file when the minikube cluster is later destroyed. When repeatedly creating and destroying minikube profiles in order to iteratively test tweaks to a particular image, this can result in /tmp filling up and causing the machine itself to run out of memory or disk space (depending on what backs /tmp). See https://gitlab.com/subprovisioner/subprovisioner/-/merge_requests/24 for a workaround added to bypass minikube's behavior.What's more, while some of minikube's files in /tmp are obvious (such as /tmp/minikube_XXXX_0.log), the filename chosen for image load is not (/tmp/build.NNN.tar). It is always good practice to make temporary file names include details about where to look when trying to debug when /tmp gets full, and fixing the temporary file to be something like /tmp/minikube_load_build.NNN.tar would fit this bill better.
Attach the log file
log.txt
Operating System
Redhat/Fedora
Driver
Podman
The text was updated successfully, but these errors were encountered: