images
The default hyper images will show all top level images, their repository and tags, and their virtual size.
Docker images have intermediate layers that increase reusability, decrease disk usage, and speed up build by allowing each step to be cached. These intermediate layers are not shown by default.
The VIRTUAL SIZE is the cumulative space taken up by the image and all its parent images. This is also the disk space used by the contents of the Tar file created when you hyper save an image.
An image will be listed more than once if it has multiple repository names or tags. This single image (identifiable by its matching IMAGE ID) uses up the VIRTUAL SIZE listed only once.
Listing the most recently created images
Listing images by name and tag
The hyper images command takes an optional [REPOSITORY[:TAG]] argument that restricts the list to images that match the argument. If you specify REPOSITORYbut no TAG, the hyper images command lists all images in the given repository.
For example, to list all images in the "java" repository, run this command :
The [REPOSITORY[:TAG]] value must be an "exact match". This means that, for example, hyper images jav does not match the image java.
If both REPOSITORY and TAG are provided, only images matching that repository and tag are listed. To find all local images in the "java" repository with tag "8" you can use:
If nothing matches REPOSITORY[:TAG], the list is empty.
Listing the full length image IDs
Listing image digests
Images that use the v2 or later format have a content-addressable identifier called a digest. As long as the input used to generate the image is unchanged, the digest value is predictable. To list image digest values, use the --digests flag:
When pushing or pulling to a 2.0 registry, the push or pull command output includes the image digest. You can pull using a digest value. You can also reference by digest in create, run, and rmi commands, as well as the FROM image reference in a Dockerfile.
Filtering
The filtering flag (-f or --filter) format is of "key=value". If there is more than one filter, then pass multiple flags (e.g., --filter "foo=bar" --filter "bif=baz")
The currently supported filters are:
dangling (boolean - true or false)
label (
label=<key>orlabel=<key>=<value>)
Untagged images (dangling)
This will display untagged images, that are the leaves of the images tree (not intermediary layers). These images occur when a new build of an image takes the repo:tag away from the image ID, leaving it as <none>:<none> or untagged. A warning will be issued if trying to remove an image when a container is presently using it. By having this flag it allows for batch cleanup.
Ready for use by hyper rmi ..., like:
NOTE: Hyper will warn you if any containers exist that are using these untagged images.
Labeled images
The label filter matches images based on the presence of a label alone or a label and a value.
The following filter matches images with the com.example.version label regardless of its value.
The following filter matches images with the com.example.version label with the 1.0 value.
In this example, with the 0.1 value, it returns an empty set because no matches were found.
Last updated