Skip to content

fix: use single registry for push-by-digest to fix manifest merge#19

Merged
Mairuis merged 1 commit into
mainfrom
fix/docker-multiregistry-push-by-digest
Feb 16, 2026
Merged

fix: use single registry for push-by-digest to fix manifest merge#19
Mairuis merged 1 commit into
mainfrom
fix/docker-multiregistry-push-by-digest

Conversation

@Mairuis
Copy link
Copy Markdown
Contributor

@Mairuis Mairuis commented Feb 16, 2026

Summary

  • Fix the merge job failing with not found when creating manifest lists for Docker Hub
  • Remove the second name=ghcr.io/... from the build job's push-by-digest output, so digests are only pushed to Docker Hub
  • Update the GHCR manifest creation step to reference digests from Docker Hub instead of GHCR

Root Cause

The build job specified two name values in a single type=image output:

type=image,name=langgenius/dify-agentbox,name=ghcr.io/langgenius/dify-agentbox,push-by-digest=true,...

In push-by-digest mode with name-canonical=true, buildx only pushed the image layers to GHCR (the second name), not Docker Hub. The merge job then tried to reference these digests on Docker Hub and failed with not found.

Fix

Follow the Docker official docs pattern: push-by-digest to a single registry (Docker Hub), then use imagetools create in the merge job to create manifest lists for both Docker Hub and GHCR from the same source digests.

@github-actions
Copy link
Copy Markdown

Super-linter summary

Language Validation result
YAML Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter

@Mairuis Mairuis force-pushed the fix/docker-multiregistry-push-by-digest branch from 72f64b8 to 2691cb0 Compare February 16, 2026 06:09
@github-actions
Copy link
Copy Markdown

Super-linter summary

Language Validation result
YAML Pass ✅

All files and directories linted successfully

For more information, see the GitHub Actions workflow run

Powered by Super-linter

@Mairuis Mairuis merged commit e7e1698 into main Feb 16, 2026
5 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants