Skip to content
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

GitHub Workflows: Fix crane for several registries #4076

Merged
merged 1 commit into from
Apr 25, 2023

Conversation

bayandin
Copy link
Member

@bayandin bayandin commented Apr 25, 2023

Describe your changes

Follow-up fix after #4067

Fixes the following error:

+ crane tag neondatabase/vm-compute-node-v14:3064 latest
Error: fetching "neondatabase/vm-compute-node-v14:3064": GET https://index.docker.io/v2/neondatabase/vm-compute-node-v14/manifests/3064: MANIFEST_UNKNOWN: manifest unknown; unknown tag=3064

https://github.com/neondatabase/neon/actions/runs/4800125634/jobs/8540963315

Eventually, I reverted back the previous approach for promoting images (login to one registry, save images to local fs, logout and login to another registry, and push images from local fs). It turns out what works for one Google project (kaniko), doesn't work for another (crane) [sigh]

Issue ticket number and link

Checklist before requesting a review

  • I have performed a self-review of my code.
  • If it is a core feature, I have added thorough tests.
  • Do we need to implement analytics? if so did you add the relevant metrics to the dashboard?
  • If this PR requires public announcement, mark it with /release-notes label and add several sentences in this section.

Checklist before merging

  • Do not forget to reformat commit message to not include the above checklist

@github-actions
Copy link

github-actions bot commented Apr 25, 2023

Test results for 9b1a10a:


debug build: 219 tests run: 209 passed, 0 failed, 10 (full report)


release build: 219 tests run: 209 passed, 0 failed, 10 (full report)


@bayandin bayandin force-pushed the bayandin/fix-promote-images branch from c8ed541 to 069f21f Compare April 25, 2023 17:54
Copy link
Member

@koivunej koivunej left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

My crane-fu is quite absent but if this fixes the build let's try it.

@bayandin bayandin force-pushed the bayandin/fix-promote-images branch 7 times, most recently from 1897660 to ae3b738 Compare April 25, 2023 21:01
@bayandin bayandin force-pushed the bayandin/fix-promote-images branch 4 times, most recently from f1cb862 to a7394d8 Compare April 25, 2023 22:14
@bayandin bayandin force-pushed the bayandin/fix-promote-images branch from a7394d8 to 9b1a10a Compare April 25, 2023 22:29
@bayandin bayandin changed the title GitHub Workflows: Push vm-compute-node images to docker hub GitHub Workflows: Fix crane for several registries Apr 25, 2023
@bayandin bayandin merged commit 2d6fd72 into main Apr 25, 2023
@bayandin bayandin deleted the bayandin/fix-promote-images branch April 25, 2023 22:59
EOF
echo "{\"credsStore\":\"ecr-login\"}" > /github/home/.docker/config.json

- name: Copy vm-compute-node images to Docker Hub
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

nit: We're not copying in this step

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.

4 participants