Skip to content

fix: check image workflow is failing for external images #9951

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

Merged
merged 1 commit into from
Feb 2, 2022

Conversation

harshithmullapudi
Copy link
Contributor

What

Added a new check for github container registry images in check_image_exists workflow

@harshithmullapudi
Copy link
Contributor Author

harshithmullapudi commented Feb 1, 2022

@cgardens what do you think of this?

@harshithmullapudi harshithmullapudi force-pushed the harshith/check-image-changes branch from 1fc4f13 to 7f12f44 Compare February 1, 2022 07:59
@harshithmullapudi harshithmullapudi temporarily deployed to more-secrets February 1, 2022 08:01 Inactive
# manifest API similar to docker so added this check
IMAGE_WITH_VERSION="$1":"$2"
printf "\tIMAGE WITH VERSION: %s\n" "$IMAGE_WITH_VERSION"
docker pull $IMAGE_WITH_VERSION
Copy link
Contributor

Choose a reason for hiding this comment

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

is there a url that we can curl instead of actually pulling the image down? the approach for dockerhub is to just to a get request to see that the image exists. does ghcr do something similar? if so we should prefer it.

Copy link
Contributor

Choose a reason for hiding this comment

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

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Yeah, you would need token and authentication to do that. Since the number of images are less can we do that once they bring up a public API similar to docker

Or is it that we want to add token and use it? What do you folks suggest?

Copy link
Contributor

Choose a reason for hiding this comment

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

The post mentioned that if it is a public image, a fake token is sufficient. We are dealing with public images, right? If that's the case, I think it's worth trying it.

Otherwise, I think it is fine to pull the image then. Feel free to merge it.

Copy link
Contributor Author

Choose a reason for hiding this comment

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

Makes sense. Let me try it with fake token

@harshithmullapudi harshithmullapudi force-pushed the harshith/check-image-changes branch from 7f12f44 to c033c89 Compare February 2, 2022 09:12
@harshithmullapudi harshithmullapudi force-pushed the harshith/check-image-changes branch from c033c89 to 8b3b23b Compare February 2, 2022 09:14
@harshithmullapudi harshithmullapudi temporarily deployed to more-secrets February 2, 2022 09:16 Inactive
@harshithmullapudi harshithmullapudi merged commit c21e2e4 into master Feb 2, 2022
@harshithmullapudi harshithmullapudi deleted the harshith/check-image-changes branch February 2, 2022 10:01
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.

3 participants