Metaplay Docs

Appearance

metaplay image list ENVIRONMENT [flags]

List Docker images in the target environment's image repository

metaplay image list ENVIRONMENT [flags] ​

List Docker images in the target environment's image repository, newest built first.

Tags naming the same image are listed together on one row.

BUILT is when the image was built, read from its config. The registry protocol does not report when an image was pushed, so re-pushing an old image does not change it.

SIZE is the compressed size of the image's config and layers as the registry stores them, over every platform of a multi-platform image, counting a layer the platforms share once. It is smaller than 'docker images' reports for an unpacked image, and for a multi-platform image larger than a single platform's download.

Every tag is read to find when its image was built, so listing a repository with many tags takes a while even with --limit. --concurrency sets how many requests are made to the registry at once: raise it for a registry that keeps up, or lower it for one that throttles or fails under load.

Expected arguments:

  • ENVIRONMENT -- Target environment name or id, eg, 'lovely-wombats-build-nimbly'.

Related commands:

  • Pull an image to the local machine using 'metaplay image pull ...'.
  • Push a built image to the repository using 'metaplay image push ...'.

Examples ​

sh
# List the 20 most recently built images in environment 'lovely-wombats-build-nimbly'.
metaplay image list lovely-wombats-build-nimbly
# List all images in JSON format.
metaplay image list lovely-wombats-build-nimbly --format=json --limit=0

Flags ​

  • --concurrency <int>: Maximum number of requests to the registry at once (default: 64)
  • --format <string>: Output format: 'text' or 'json' (default: text)
  • --limit <int>: Maximum number of images to show (0 for all) (default: 20)

Inherited Flags ​

  • --color <string>: Should the output be colored (yes/no/auto)? [env: METAPLAYCLI_COLOR] (default: auto)
  • --project <string>: Path to the to project directory (where metaplay-project.yaml is located)
  • --skip-version-check: Skip the check for a new CLI version being available
  • --verbose: Enable verbose logging, useful for troubleshooting [env: METAPLAYCLI_VERBOSE]