dask-docker - GitLite

KO | EN

gitlite — search

#hacktoberfest #react #typescript #go #android #machine-learning #rust #linux #docker #nodejs #cli #kubernetes #ios #open-source

dask-docker

(★ 243)

Docker images for dask

파일 탐색기

최종 버전 다운로드 (.zip)

- - automerge.yml
  - autotag.yml
  - build.yml
  - watch-conda-forge.yml
- Dockerfile
- prepare.sh
- docker-compose.yml
- - 01-custom-delayed.ipynb
  - 02-custom-futures.ipynb
  - 03-dataframes-timeseries.ipynb
  - 04-dask-array.ipynb
  - 05-nyc-taxi.ipynb
  - 06-nyc-parquet.ipynb
- Dockerfile
- prepare.sh
- run.sh
.gitattributes
CONTRIBUTING.md
docker-compose.yml
LICENSE
README.md

# 설치 가이드

1. 코드 내려받기

git clone https://github.com/dask/dask-docker

깃허브에서 프로젝트 코드 전체를 내 컴퓨터로 내려받습니다.

cd dask-docker

방금 내려받은 프로젝트 폴더 안으로 이동합니다.

2. Docker

쉬움 추천

사전 준비물

Git GitHub에서 프로젝트 코드를 내려받으려면 필요합니다.
Docker Desktop 컨테이너를 빌드하고 실행하려면 필요합니다. 설치 후 실행해서 백그라운드에 켜두세요.

docker-compose up

compose 설정 파일에 정의된 서비스들을 대상으로 명령을 실행합니다.

docker run -e EXTRA_CONDA_PACKAGES="-c dask/label/dev dask" daskdev/dask:latest

빌드된 이미지를 실제 컨테이너로 실행합니다.

docker-compose build

compose 설정 파일에 정의된 서비스들을 대상으로 명령을 실행합니다.

docker-compose build notebook

compose 설정 파일에 정의된 서비스들을 대상으로 명령을 실행합니다.

docker buildx bake --progress=plain --set *.platform=linux/arm64,linux/amd64 --push docker-stacks-foundation

Dockerfile을 기반으로 실행 가능한 이미지를 빌드합니다.

✅ 터미널에 docker compose ps 를 입력해 컨테이너들이 Up 상태인지 확인하세요. README에 포트 번호가 적혀있다면 브라우저에서 http://localhost:포트번호 로 접속해보세요.

이 레포의 README에 적힌 실제 명령어를 그대로 가져왔습니다.

// repository documentation

Was this content helpful?

★ 0 (0 ratings)

# Dask docker images

[![Docker build](https://github.com/dask/dask-docker/actions/workflows/build.yml/badge.svg)](https://github.com/dask/dask-docker/actions/workflows/build.yml)

| Image  | Description | Versions |
| ------------- | ------------- | ------------- |
| `ghcr.io/dask/dask`  | Base image to use for Dask scheduler and workers  |   [![][daskdev-dask-py310-release] ![][daskdev-dask-release] ![][daskdev-dask-latest] <br /> ![][daskdev-dask-py310-release] <br /> ![][daskdev-dask-py311-release] <br /> ![][daskdev-dask-py312-release] <br /> ![][daskdev-dask-py313-release] <br /> ![][daskdev-dask-py314-release]](https://github.com/dask/dask-docker/pkgs/container/dask)  |
| `ghcr.io/dask/dask-notebook`  | Jupyter Notebook image to use as helper entrypoint  | [![][daskdev-dask-notebook-py310-release] ![][daskdev-dask-notebook-release] ![][daskdev-dask-notebook-latest] <br /> ![][daskdev-dask-notebook-py310-release] <br /> ![][daskdev-dask-notebook-py311-release] <br /> ![][daskdev-dask-notebook-py312-release] <br /> ![][daskdev-dask-notebook-py313-release] <br /> ![][daskdev-dask-notebook-py314-release]](https://github.com/dask/dask-docker/pkgs/container/dask-notebook) |

[daskdev-dask-latest]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask-latest-blue
[daskdev-dask-release]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask-2026.7.1-blue
[daskdev-dask-py310-release]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask-2026.7.1--py3.10-blue
[daskdev-dask-py311-release]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask-2026.7.1--py3.11-blue
[daskdev-dask-py312-release]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask-2026.7.1--py3.12-blue
[daskdev-dask-py313-release]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask-2026.7.1--py3.13-blue
[daskdev-dask-py314-release]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask-2026.7.1--py3.14-blue
[daskdev-dask-notebook-latest]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask--notebook-latest-blue
[daskdev-dask-notebook-release]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask--notebook-2026.7.1-blue
[daskdev-dask-notebook-py310-release]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask--notebook-2026.7.1--py3.10-blue
[daskdev-dask-notebook-py311-release]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask--notebook-2026.7.1--py3.11-blue
[daskdev-dask-notebook-py312-release]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask--notebook-2026.7.1--py3.12-blue
[daskdev-dask-notebook-py313-release]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask--notebook-2026.7.1--py3.13-blue
[daskdev-dask-notebook-py314-release]: https://img.shields.io/badge/ghcr.io%2Fdask%2Fdask--notebook-2026.7.1--py3.14-blue

## Example

An example `docker-compose.yml` file is included for starting a small cluster.

```bash
docker-compose up
```

Open the notebook using the URL that is printed by the output so it has the token.

On a new notebook run:

```python
from dask.distributed import Client
client = Client()  # The address is automatically set by the DASK_SCHEDULER_ADDRESS environment variable
client.ncores()
```

It should output something like this:

```python
{'tcp://172.23.0.4:41269': 4}
```

## Environment Variables

The following environment variables are supported for both the base and notebook images:

* `$EXTRA_APT_PACKAGES` - Space separated list of additional system packages to install with apt.
* `$EXTRA_CONDA_PACKAGES` - Space separated list of additional packages to install with conda.
This variable can also be used to specify custom conda channels; for example, to install the latest Dask conda nightly packages:

```bash
docker run -e EXTRA_CONDA_PACKAGES="-c dask/label/dev dask" daskdev/dask:latest
```

* `$EXTRA_PIP_PACKAGES` - Space separated list of additional python packages to install with pip.
* `$USE_MAMBA` - Boolean controlling whether to use conda or mamba to install `$EXTRA_CONDA_PACKAGES`.

The notebook image supports the following additional environment variables:

* `$JUPYTERLAB_ARGS` - Extra [arguments](https://jupyter-notebook.readthedocs.io/en/stable/config.html) to pass to the `jupyter lab` command.

## Building images

Docker compose provides an easy way to building all the images with the right context

```bash
cd build

# Use legacy builder as buildkit still doesn't support subdirectories when building from git repos
export DOCKER_BUILDKIT=0
export COMPOSE_DOCKER_CLI_BUILD=0

docker-compose build

# Just build one image e.g. notebook
docker-compose build notebook
```

### Cross building

The images can be cross-built using `docker buildx bake`. However buildx bake does not listen to `depends_on` (since in theory that is only a runtime not a build time constraint https://github.com/docker/buildx/issues/447). To work around this we first need to build the "docker-stacks-foundation" image.

```bash
cd build

# If you have permission to push to daskdev/
docker buildx bake --progress=plain --set *.platform=linux/arm64,linux/amd64 --push docker-stacks-foundation
docker buildx bake --progress=plain --set *.platform=linux/arm64,linux/amd64 --push

# If you don'tset DOCKERUSER to your dockerhub username.
export DOCKERUSER=holdenk
docker buildx bake --progress=plain --set *.platform=linux/arm64,linux/amd64 --set docker-stacks-foundation.tags.image=${DOCKERUSER}/docker-stacks-foundation:lab-py38 --push docker-stacks-foundation
docker buildx bake --progress=plain --set *.platform=linux/arm64,linux/amd64 --set scheduler.tags=${DOCKERUSER}/dask --set worker.tags=${DOCKERUSER}/dask --set notebook.tags=${DOCKERUSER}/dask-notebook --set docker-stacks-foundation.tags=${DOCKERUSER}/docker-stacks-foundation:lab-py38 --set notebook.args.base=${DOCKERUSER} --push
```

## Releasing

Building and releasing new image versions is done automatically.

- When a new Dask version is released the `watch-conda-forge` action will trigger and open a PR to update the latest release version in this repo.
- If images build successfully that PR will be automatically merged by the `automerge` action.
- When a PR like this is merged which updates the pinned release version a tag is automatically created to match that version by the `autotag` action.
- When tags are created a new image is built and pushed using the `docker/build-push-action` action.