-
Notifications
You must be signed in to change notification settings - Fork 2
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Wrong digest Output after pushing to GCP Artifact #242
Comments
Hi @NikitaSemenovAiforia, a few clarifying questions.
|
Confirmed.
Client: Docker Engine - Community buildx v0.16.2
Yes. The old script for this job was running simultaneously. Here is the step: - id: build_and_push
name: Build and push
uses: docker/build-push-action@v6
with:
push: true
tags: ${{ vars.BASE_DOCKER_HUB_URL }}/${{ vars.PROJECT_NAME }}/docker-repository/transport-layer-migrator:k8s
target: 'migration'
cache-from: type=registry,ref=${{ vars.BASE_DOCKER_HUB_URL }}/${{ vars.PROJECT_NAME }}/docker-repository/transport-layer-migrator:k8s
cache-to: type=inline |
Super helpful context, thank you @NikitaSemenovAiforia! I haven't been able to reproduce this yet -- the digest we use should be returned by the daemon whenever we export something to the registry. One thing you might try is changing this cache-to entry:
to an inline cache ( |
What happened?
I set registries to GCP Artifact URL. The image was pushed. But digest Output is set to docker.io/library/sha256:.
There are no other registries or exports except GitHub cache.
Example
Output of
pulumi about
CLI
Version 3.126.0
Go Version go1.22.5
Go Compiler gc
Plugins
KIND NAME VERSION
resource docker-build 0.0.6
resource gcp 7.38.0
language python unknown
Host
OS ubuntu
Version 22.04
Arch x86_64
This project is written in python: python' version='3.12.1'
Dependencies:
NAME VERSION
pip 24.2
pulumi_docker_build 0.0.6
pulumi_gcp 7.38.0
pyright 1.1.378
setuptools 74.0.0
wheel 0.44.0
Additional context
No response
Contributing
Vote on this issue by adding a 👍 reaction.
To contribute a fix for this issue, leave a comment (and link to your pull request, if you've opened one already).
The text was updated successfully, but these errors were encountered: