$ minishift delete --clear-cache
To speed up the provisioning of the OpenShift cluster and to minimize network traffic, container images can be cached on the host.
These images can then be imported into the running Docker daemon, either explicitly on request or implicitly during minishift start.
The following sections describe image caching and its configuration in more detail.
|
The format in which images are cached has changed with Minishift version 1.10.0. Prior to 1.10.0 the images were stored as tar files. As of 1.10.0, images are stored in the OCI image format. If you used image caching prior to Minishift 1.10.0, your cache will need to be recreated. If you want to remove the obsolete pre 1.10.0 images, you can clear your cache via: $ minishift delete --clear-cache |
Minishift provides the image command together with its sub-commands to control the behavior of image caching.
To export and import images from the Docker daemon of the Minishift VM, use minishift image export and minishift image import.
Once the Minishift VM is running, images can be explicitly exported from the Docker daemon:
$ minishift image export <image-name-0> <image-name-1> ... Pulling image <image-name-0> .. OK Exporting <image-name-0>. OK Pulling image <image-name-1> .. OK Exporting <image-name-2>. OK
|
Images which are not available in the Docker daemon will be pulled prior to being exported to the host. |
To import previously cached images, use the minishift image import command:
$ minishift image import <image-name-0> <image-name-1> ... Importing <image-name-0> . OK
The minishift image list command lists either the currently cached images or the images available in the Minishift Docker daemon.
To view currently cached images on the host:
$ minishift image list openshift/origin-docker-registry:v3.6.0 openshift/origin-haproxy-router:v3.6.0 openshift/origin:v3.6.0
To view images available in the Docker daemon:
$ minishift image list --vm openshift/origin-deployer:v3.6.0 openshift/origin-docker-registry:v3.6.0 openshift/origin-haproxy-router:v3.6.0 openshift/origin-pod:v3.6.0 openshift/origin:v3.6.0
In order to avoid having to type the image names explicitly as part of the image export or image import command, you can store a list of image names for import and export in the persistent configuration.
Use minishift image cache-config view to view the list of currently configured images and minishift image cache-config add to add images to the list:
$ minishift image cache-config view $ minishift image cache-config add alpine:latest busybox:latest $ minishift image cache-config view alpine:latest busybox:latest
To remove images from the list use minishift image cache-config remove:
$ minishift image cache-config remove alpine:latest $ minishift image cache-config view busybox:latest
Once the image names are stored in the persistent configuration, you can run minishift image export and minishift image import without any arguments.
You can export and import all images using the --all flag.
For the export command, this means that all images currently available on the Docker daemon will be exported to the host.
For the import command, it means that all images available in the local Minishift cache will be imported into the Docker daemon of the Minishift VM.
|
Exporting and importing all images can take a long time and locally cached images can take up a considerable amount of disk space. We recommend using this feature with caution. |
Image caching is enabled by default for Minishift.
It occurs in a background process after the minishift start command is completed for the first time.
Once the images are cached under $MINISHIFT_HOME/cache/images, successive Minishift VM creations will use these cached images.
To disable this feature you need to disable the image-caching property in the persistent configuration using the minishift config set command:
$ minishift config set image-caching false
|
Implicit image caching will transparently add the required OpenShift images to the list of cached images as specified per |
|
Each time an image exporting background process runs, a log file is generated under $MINISHIFT_HOME/logs which can be used to verify the progress of the export. |
You can re-enable the caching of the OpenShift images by setting image-caching to true or removing the setting altogether using minishift config unset:
$ minishift config unset image-caching