Repository navigation
Publish CloudInvoke images to two registries - #250
Merged
Merged
Conversation
Send each release image to Docker Hub under the CloudInvoke namespace and to GitHub Container Registry. Keep the existing versioned variants and architectures, and label the images with their source, license, and publisher. Align local image names with the published tags and ignore component crate tags when choosing the unFTP image version.
This was referenced Oct 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Publish the three existing multi-architecture release images to both
cloudinvoke/unftpon Docker Hub andghcr.io/cloudinvoke/unftp.The Docker Hub namespace follows the repository variable
DOCKERHUB_NAMESPACE, which is already set tocloudinvoke.Add OCI source, Apache-2.0 license, and CloudInvoke vendor labels to
the release Dockerfiles and local build templates. Update the local
image names and user documentation for the new registries. Restrict
version lookup to unFTP tags so component crate releases do not become
container image versions.
Validation
git diff --checkand inspectedmake -n docker-image-alpine.The image push job runs on a GitHub release, so CI on this PR will not
publish images. After the first GHCR push, make the new package public
in the Cloudinvoke organization.