DirectorySecurity AdvisoriesPricing
/
Sign in
Directory
dagster logo

dagster

packaged by Chainguard

Last changed
Request a free trial

Contact our team to test out this image for free. Please also indicate any other images you would like to evaluate.

Tags
Overview
Comparison
Provenance
Specifications
SBOM
Vulnerabilities
Advisories

Chainguard Container for dagster

Dagster data orchestration platform for building and maintaining data assets.

Chainguard Containers are regularly-updated, secure-by-default container images.

Download this Container Image

For those with access, this container image is available on cgr.dev:

docker pull cgr.dev/ORGANIZATION/dagster:latest

Be sure to replace the ORGANIZATION placeholder with the name used for your organization's private repository within the Chainguard Registry.

Compatibility Notes

This image is a drop-in replacement for the upstream dagster/dagster-k8s Docker image. It includes the same pip packages as upstream:

  • dagster, dagster-webserver, dagster-daemon, dagster-graphql
  • Cloud integrations: dagster-aws, dagster-gcp, dagster-azure
  • Infrastructure: dagster-k8s, dagster-postgres, grpcio

The image runs as nonroot (UID 65532) with the venv at /opt/chainguard/dagster. The default command is python3. The /opt/dagster/dagster_home directory is pre-created and writable by the nonroot user for use as DAGSTER_HOME (set by the Helm chart at deploy time).

Usage

Quick Start

Verify the image works:

docker run --rm cgr.dev/ORGANIZATION/dagster:latest dagster --version

Run the Dagster development server with a simple asset definition:

docker run --rm -p 3000:3000 cgr.dev/ORGANIZATION/dagster:latest \
    dagster dev -h 0.0.0.0 -p 3000 -f /path/to/your/definitions.py

Running Components Individually

# Start the webserver
docker run --rm cgr.dev/ORGANIZATION/dagster:latest dagster-webserver -h 0.0.0.0

# Start the daemon
docker run --rm cgr.dev/ORGANIZATION/dagster:latest dagster-daemon run

# Run a GraphQL server
docker run --rm cgr.dev/ORGANIZATION/dagster:latest dagster-graphql

Deployment

Helm Chart

Add the Dagster Helm repository:

helm repo add dagster https://dagster-io.github.io/helm
helm repo update

Create a values.yaml to use Chainguard images:

dagsterWebserver:
  image:
    repository: cgr.dev/ORGANIZATION/dagster
    tag: latest

dagsterDaemon:
  image:
    repository: cgr.dev/ORGANIZATION/dagster
    tag: latest

Note: Depending on your use case, you may also need to update image.repository and image.tag under the runLauncher option in the Helm chart to ensure run execution pods use the same Chainguard image.

Install the chart:

helm install dagster dagster/dagster -f values.yaml

Documentation and Resources

What are Chainguard Containers?

Chainguard's free tier of Starter container images are built with Wolfi, our minimal Linux undistro.

All other Chainguard Containers are built with Chainguard OS, Chainguard's minimal Linux operating system designed to produce container images that meet the requirements of a more secure software supply chain.

The main features of Chainguard Containers include:

For cases where you need container images with shells and package managers to build or debug, most Chainguard Containers come paired with a development, or -dev, variant.

In all other cases, including Chainguard Containers tagged as :latest or with a specific version number, the container images include only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager.

Although the -dev container image variants have similar security features as their more minimal versions, they include additional software that is typically not necessary in production environments. We recommend using multi-stage builds to copy artifacts from the -dev variant into a more minimal production image.

Need additional packages?

To improve security, Chainguard Containers include only essential dependencies. Need more packages? Chainguard customers can use Custom Assembly to add packages, either through the Console, chainctl, or API.

To use Custom Assembly in the Chainguard Console: navigate to the image you'd like to customize in your Organization's list of images, and click on the Customize image button at the top of the page.

Learn More

Refer to our Chainguard Containers documentation on Chainguard Academy. Chainguard also offers VMs and Librariescontact us for access.

Trademarks

This software listing is packaged by Chainguard. The trademarks set forth in this offering are owned by their respective companies, and use of them does not imply any affiliation, sponsorship, or endorsement by such companies.

Licenses

Chainguard's container images contain software packages that are direct or transitive dependencies. The following licenses were found in the "latest" tag of this image:

  • Apache-2.0

  • BSD-2-Clause

  • CC-PDDC

  • GCC-exception-3.1

  • GPL-2.0-only

  • GPL-2.0-or-later

  • GPL-3.0-or-later

For a complete list of licenses, please refer to this Image's SBOM.

Software license agreement

Compliance

Chainguard Containers are SLSA Level 3 compliant with detailed metadata and documentation about how it was built. We generate build provenance and a Software Bill of Materials (SBOM) for each release, with complete visibility into the software supply chain.

SLSA compliance at Chainguard

This image helps reduce time and effort in establishing PCI DSS 4.0 compliance with low-to-no CVEs.

PCI DSS at Chainguard

A FIPS validated version of this image is available for FedRAMP compliance. STIG is included with FIPS image.


Related images
dagster-fips logoFIPS
dagster-fips

Category
Application

The trusted source for open source

Talk to an expert
PrivacyTerms

Product

Chainguard ContainersChainguard LibrariesChainguard VMsChainguard OS PackagesChainguard ActionsChainguard Agent SkillsIntegrationsPricing
© 2026 Chainguard, Inc. All Rights Reserved.
Chainguard® and the Chainguard logo are registered trademarks of Chainguard, Inc. in the United States and/or other countries.
The other respective trademarks mentioned on this page are owned by the respective companies and use of them does not imply any affiliation or endorsement.