Chainguard Container for dask-gateway-server

A multi-tenant server for securely deploying and managing Dask clusters.

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/dask-gateway-server:latest

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

Compatibility Notes

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.

Getting Started

To get started, first create a pair of environment variables to hold the names of the Helm release and the Kubernetes namespace, respectively:

RELEASE=dask-gateway
NAMESPACE=dask-gateway

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:

  backend:
    image:
      name: cgr.dev/ORGANIZATION/dask-gateway
      tag: latest
      pullPolicy:

Next, install the Dask Gateway Helm chart by running the following command:

helm upgrade $RELEASE dask-gateway \
    --repo=https://helm.dask.org \
    --install \
    --namespace $NAMESPACE \
    --create-namespace \
    --values values.yaml

Once the resources have been created, run the following command to ensure that the services are running:

kubectl get service --namespace dask-gateway

NAME               	TYPE       	CLUSTER-IP  	EXTERNAL-IP  	PORT(S)    	AGE
api-dask-gateway   	ClusterIP  	10.96.107.183   <none>       	8000/TCP   	134m
traefik-dask-gateway   LoadBalancer   10.96.236.132   146.148.58.187   80:31487/TCP   134m

Additionally, run the following command to ensure the daskcluster CRD was installed:

kubectl get daskcluster -o yaml

apiVersion: v1
items: []
kind: List
metadata:
  resourceVersion: ""
  selfLink: ""

Documentation and Resources

• Official Dask Gateway documentation
• Default values.yaml file for Dask Gateway

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:

• Minimal design, without unnecessary software bloat
• Daily builds to ensure container images are up-to-date with available security patches
• High quality build-time SBOMs attesting to the provenance of all artifacts within the image
• Verifiable signatures provided by Sigstore
• Reproducible builds with Cosign and apko (read more about reproducibility)

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 Libraries — contact 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.