From 888da6035babef0fe3c2a8e51e64b6c7f521cc35 Mon Sep 17 00:00:00 2001 From: Kevin Wang Date: Sat, 19 Sep 2026 21:05:53 -0700 Subject: [PATCH] chore(ingress): pin dstack-ingress 2.6 digest from the release build The examples still deployed 2.3: 2.4 and 2.5 were tagged and published without this commit, so for two releases the compose files and README snippets people copy pointed at an image two versions behind, and the repository held no record mapping those digests back to a commit. 2.6 also moves the image to GHCR, so the registry changes with the tag and digest. Digest sha256:c212abb7 is what the release workflow pushed from 91a5819, and what a local ./build-image.sh on a separate native linux/amd64 host produced from the same commit. --- custom-domain/dstack-ingress/README.md | 6 +++--- custom-domain/dstack-ingress/docker-compose.multi.yaml | 2 +- custom-domain/dstack-ingress/docker-compose.yaml | 2 +- k3s/docker-compose.yaml | 2 +- 4 files changed, 6 insertions(+), 6 deletions(-) diff --git a/custom-domain/dstack-ingress/README.md b/custom-domain/dstack-ingress/README.md index 251aebb..2c6ce89 100644 --- a/custom-domain/dstack-ingress/README.md +++ b/custom-domain/dstack-ingress/README.md @@ -35,7 +35,7 @@ You can use a wildcard domain (e.g. `*.myapp.com`) to route all subdomains to a ```yaml services: dstack-ingress: - image: dstacktee/dstack-ingress:2.3@sha256:527c53523b9226782a11dbd800a3ff55e8a1f0b88e6224e8f7e4db7419769fbe + image: ghcr.io/dstack-tee/dstack-ingress:2.6@sha256:c212abb7bedec4d7b54a82bcf9972e58e39a4757cc811faeb6017eee6c0673b0 ports: - "443:443" environment: @@ -64,7 +64,7 @@ volumes: ```yaml services: dstack-ingress: - image: dstacktee/dstack-ingress:2.3@sha256:527c53523b9226782a11dbd800a3ff55e8a1f0b88e6224e8f7e4db7419769fbe + image: ghcr.io/dstack-tee/dstack-ingress:2.6@sha256:c212abb7bedec4d7b54a82bcf9972e58e39a4757cc811faeb6017eee6c0673b0 ports: - "443:443" environment: @@ -102,7 +102,7 @@ Use `ROUTING_MAP` to route different domains to different backends via SNI: ```yaml services: ingress: - image: dstacktee/dstack-ingress:2.3@sha256:527c53523b9226782a11dbd800a3ff55e8a1f0b88e6224e8f7e4db7419769fbe + image: ghcr.io/dstack-tee/dstack-ingress:2.6@sha256:c212abb7bedec4d7b54a82bcf9972e58e39a4757cc811faeb6017eee6c0673b0 ports: - "443:443" environment: diff --git a/custom-domain/dstack-ingress/docker-compose.multi.yaml b/custom-domain/dstack-ingress/docker-compose.multi.yaml index e7fa2d0..cc342c7 100644 --- a/custom-domain/dstack-ingress/docker-compose.multi.yaml +++ b/custom-domain/dstack-ingress/docker-compose.multi.yaml @@ -1,6 +1,6 @@ services: ingress: - image: dstacktee/dstack-ingress:2.3@sha256:527c53523b9226782a11dbd800a3ff55e8a1f0b88e6224e8f7e4db7419769fbe + image: ghcr.io/dstack-tee/dstack-ingress:2.6@sha256:c212abb7bedec4d7b54a82bcf9972e58e39a4757cc811faeb6017eee6c0673b0 ports: - "443:443" environment: diff --git a/custom-domain/dstack-ingress/docker-compose.yaml b/custom-domain/dstack-ingress/docker-compose.yaml index ff0962a..7ac3b21 100644 --- a/custom-domain/dstack-ingress/docker-compose.yaml +++ b/custom-domain/dstack-ingress/docker-compose.yaml @@ -1,6 +1,6 @@ services: dstack-ingress: - image: dstacktee/dstack-ingress:2.3@sha256:527c53523b9226782a11dbd800a3ff55e8a1f0b88e6224e8f7e4db7419769fbe + image: ghcr.io/dstack-tee/dstack-ingress:2.6@sha256:c212abb7bedec4d7b54a82bcf9972e58e39a4757cc811faeb6017eee6c0673b0 ports: - "443:443" environment: diff --git a/k3s/docker-compose.yaml b/k3s/docker-compose.yaml index 04736ce..49e8f3d 100644 --- a/k3s/docker-compose.yaml +++ b/k3s/docker-compose.yaml @@ -36,7 +36,7 @@ services: restart: unless-stopped dstack-ingress: - image: dstacktee/dstack-ingress:2.3@sha256:527c53523b9226782a11dbd800a3ff55e8a1f0b88e6224e8f7e4db7419769fbe + image: ghcr.io/dstack-tee/dstack-ingress:2.6@sha256:c212abb7bedec4d7b54a82bcf9972e58e39a4757cc811faeb6017eee6c0673b0 ports: - "443:443" environment: