Home • Explore • Blog • CI
☰



docker
1st chunk of `content/manuals/scout/integrations/environment/_index.md`
70c4fd6e57c073691eec729892246832c8f2377d8a71b37d0000000100000891
---
description:
  Docker Scout can integrate with runtime environments to give you real-time
  insights about your software supply chain.
keywords: supply chain, security, streams, environments, workloads, deployments
title: Integrating Docker Scout with environments
---

You can integrate Docker Scout with your runtime environments, and get insights
for your running workloads. This gives you a real-time view of your security
status for your deployed artifacts.

Docker Scout lets you define multiple environments, and assign images to
different environments. This gives you a complete overview of your software
supply chain, and lets you view and compare deltas between environments, for
example staging and production.

How you define and name your environments is up to you. You can use patterns
that are meaningful to you and that matches how you ship your applications.

## Assign to environments

Each environment contains references to a number of images. These references
represent containers currently running in that particular environment.

For example, say you're running `myorg/webapp:3.1` in production, you can
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
Title: Integrating Docker Scout with Runtime Environments
Summary
Docker Scout integrates with runtime environments to provide real-time insights into your software supply chain and the security status of deployed artifacts. You can define multiple environments and assign images to them, enabling a complete overview and comparison of deltas between environments. Images can be assigned to environments manually using the CLI or automatically through runtime integrations like GitHub Actions, CLI client, and Sysdig. Organization owners can create new environments and set up integrations, but images must be analyzed before they can be assigned.