Managing and Comparing Environments in Docker Scout

assign that tag to your `production` environment. You might be running a different version of the same image in staging, in which case you can assign that version of the image to the `staging` environment. To add environments to Docker Scout, you can: - Use the `docker scout env <environment> <image>` CLI command to record images to environments manually - Enable a runtime integration to automatically detect images in your environments. Docker Scout supports the following runtime integrations: - [Docker Scout GitHub Action](https://github.com/marketplace/actions/docker-scout#record-an-image-deployed-to-an-environment) - [CLI client](./cli.md) - [Sysdig integration](./sysdig.md) > [!NOTE] > > Only organization owners can create new environments and set up integrations. > Additionally, Docker Scout only assigns an image to an environment if the > image [has been analyzed](/manuals/scout/explore/analysis.md), either manually or > through a [registry integration](/manuals/scout/integrations/_index.md#container-registries). ## List environments To see all of the available environments for an organization, you can use the `docker scout env` command. ```console $ docker scout env ``` By default, this prints all environments for your personal Docker organization. To list environments for another organization that you're a part of, use the `--org` flag. ```console $ docker scout env --org <org> ``` You can use the `docker scout config` command to change the default organization. This changes the default organization for all `docker scout` commands, not just `env`. ```console $ docker scout config organization <org> ``` ## Comparing between environments Assigning images to environments lets you make comparisons with and between environments. This is useful for things like GitHub pull requests, for comparing the image built from the code in the PR to the corresponding image in staging or production. You can also compare with streams using the `--to-env` flag on the [`docker scout compare`](/reference/cli/docker/scout/compare.md) CLI command: ```console $ docker scout compare --to-env production myorg/webapp:latest ``` ## View images for an environment To view the images for an environment: 1. Go to the [Images page](https://scout.docker.com/) in the Docker Scout Dashboard. 2. Open the **Environments** drop-down menu. 3. Select the environment that you want to view. The list displays all images that have been assigned to the selected environment. If you've deployed multiple versions of the same image in an environment, all versions of the image appear in the list. Alternatively, you can use the `docker scout env` command to view the images from the terminal. ```console $ docker scout env production docker/scout-demo-service:main@sha256:ef08dca54c4f371e7ea090914f503982e890ec81d22fd29aa3b012351a44e1bc ``` ### Mismatching image tags When you've selected an environment on the **Images** tab, tags in the list represent the tag that was used to deploy the image. Tags are mutable, meaning that you can change the image digest that a tag refers to. If Docker Scout detects that a tag refers to an outdated digest, a warning icon displays next to the image name.

This section explains how to manage and compare environments within Docker Scout. You can add environments by manually using the CLI or by enabling runtime integrations. The `docker scout env` command lists available environments, optionally filtering by organization. Comparing images between environments, using the `docker scout compare` command with the `--to-env` flag, allows you to assess differences. The Docker Scout Dashboard provides a visual interface to view images assigned to an environment, and the CLI can also be used to list images in an environment. A warning is displayed if a tag refers to an outdated image digest.