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

[Bug]: Cannot pull image from gitea packages #243

Closed
ricker-flow opened this issue May 8, 2024 · 4 comments
Closed

[Bug]: Cannot pull image from gitea packages #243

ricker-flow opened this issue May 8, 2024 · 4 comments
Labels
bug Something isn't working

Comments

@ricker-flow
Copy link

What is your environment, configuration, and command?

idpbuilder 0.4.1

What did you do and What did you see instead?

I can push and pull images to Gitea from the commandline.

docker push gitea.cnoe.localtest.me:8443/deepsky/digitalasset:latest

However, Argo cannot pull the image from Gitea.

Failed to pull image "gitea.cnoe.localtest.me:8443/giteaadmin/digitalasset:latest": 
rpc error: code = Unknown desc = failed to pull and unpack image "gitea.cnoe.localtest.me:8443/giteaadmin/digitalasset:latest": 
failed to resolve reference "gitea.cnoe.localtest.me:8443/giteaadmin/digitalasset:latest": 
failed to do request: Head "https://gitea.cnoe.localtest.me:8443/v2/giteaadmin/digitalasset/manifests/latest": 
dial tcp [::1]:8443: connect: connection refused

Is that the behavior reported with go-gitea/gitea#29591 ?

Additional Information. Logs.

No response

@ricker-flow ricker-flow added the bug Something isn't working label May 8, 2024
@nabuskey
Copy link
Collaborator

This doesn't look like related to the issue linked. Likely because the domain name resolves to 127.0.0.1 inside the cluster. You can work around this by configuring core dns to resolve domain names you are interested in. This is done in the ref implementation example.

I've thinking about making it the default configuration. Any opinions here @nimakaviani @cmoulliard @csantanapr ?

@nimakaviani
Copy link
Contributor

yeah, I like the idea of making cnoe.localtest.me resolve successfully inside the k8s cluster too.

Not sure if it will lead to anti-patterns though, eg for folks to experiment with pushing to gitea manually and configuring argo cd apps out of band.

More benefits than harms though, so it is a +1 from me.

jessesanford added a commit to jessesanford/idpbuilder that referenced this issue Jun 5, 2024
@omrishiv
Copy link
Contributor

@jessesanford is this closed now from your recent PR?

@nabuskey
Copy link
Collaborator

This should work now. https://cnoe.io/docs/reference-implementation/installations/idpbuilder/local-oci-registry
Closing this but feel free to re-open

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
bug Something isn't working
Projects
None yet
Development

No branches or pull requests

4 participants