Last changed
Be the first to hear about exciting product updates, critical vulnerability alerts, compare alternative images, and more.
Sign UpA multi-tenant server for securely deploying and managing Dask clusters.
Chainguard Containers are regularly-updated, secure-by-default container images.
For those with access, this container image is available on cgr.dev
:
Be sure to replace the ORGANIZATION
placeholder with the name used for your organization's private repository within the Chainguard Registry.
Chainguard's Dask Gateway container is comparable to the daskgateway/dask-gateway image maintained by Dask. Like most of Chainguard's container images, the Dask Gateway image was designed for minimalism and does not include things like a shell or package manager.
To get started, first create a pair of environment variables to hold the names of the Helm release and the Kubernetes namespace, respectively:
This example uses the name dask-gateway
for both variables, but you can name the Helm release and Kubernetes namespace anything you'd like.
Next, you need to set up a values file. The Dask Gateway Helm chart offers many configuration options allowing you to create a setup that suits your exact needs. You can use the default values.yaml
file as a basis for your own. The default file also includes explanations for many of the available configuration options.
Be sure to edit the values.yaml
file to point to Chainguard's Dask Gateway image instead of the upstream alternative:
Next, install the Dask Gateway Helm chart by running the following command:
Once the resources have been created, run the following command to ensure that the services are running:
Additionally, run the following command to ensure the daskcluster
CRD was installed:
Chainguard Containers are minimal container images that are secure by default.
In many cases, the Chainguard Containers tagged as :latest
contain only an open-source application and its runtime dependencies. These minimal container images typically do not contain a shell or package manager. Chainguard Containers are built with Wolfi, our Linux undistro 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 -dev
variant.
Although the -dev
container image variants have similar security features as their more minimal versions, they feature additional software that is typically not necessary in production environments. We recommend using multi-stage builds to leverage the -dev
variants, copying application artifacts into a final minimal container that offers a reduced attack surface that won’t allow package installations or logins.
To better understand how to work with Chainguard Containers, please visit Chainguard Academy and Chainguard Courses.
In addition to Containers, Chainguard offers VMs and Libraries. Contact Chainguard to access additional products.
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.
Chainguard 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
BSD-3-Clause
GCC-exception-3.1
GPL-3.0-or-later
LGPL-2.1-or-later
MIT
For a complete list of licenses, please refer to this Image's SBOM.
Software license agreement