abra catalogue generate
chokes on non-DockerHub-hosted images #258
Labels
No Label
abra
abra-gandi
awaiting-feedback
backups
bug
build
ci/cd
community organising
contributing
coopcloud.tech
democracy
design
documentation
duplicate
enhancement
finance
funding
good first issue
help wanted
installer
kadabra
performance
proposal
question
recipes.coopcloud.tech
security
test
wontfix
No Milestone
No project
No Assignees
2 Participants
Notifications
Due Date
No due date set.
Dependencies
No dependencies set.
Reference: coop-cloud/organising#258
Loading…
Reference in New Issue
No description provided.
Delete Branch "%!s(<nil>)"
Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?
Steps to reproduce
abra catalogue generate hedgedoc
(Where Hedgedoc's image is
quay.io/hedgedoc/hedgedoc
)Describe the expected behavior
Looks up image tag info from
quay.io
Describe the current behavior
Tries to look up the info from
https://index.docker.io/v2/hedgedoc/hedgedoc/manifests/1.8.2
, duly fails:Any idea how this might be fixed?
A huge bag of hacks in
abra/pkg/client/registry.go
?Additional information
dd0f328
Hmmm right. Happy to see that skopeo does provide quay support (which is where I based my docker hub support logic from) so I think it just requires some digging in https://github.com/containers/skopeo for the right URLs to do the token dance. We might need to do some inspection to figure out which registry we need to ask? Not sure but this will need some investigation.
Additional report in #296. We might want to figure out how to handle this sometime soon. These recipes can still be loaded into the catalogue by hand but that is not ideal.
Happy to say I think this issue is squashed with coop-cloud/abra#159 on latest HEAD. I've been doing some testing, hopefully it will stand up to other user cases. Lemme know ✌️