-
Notifications
You must be signed in to change notification settings - Fork 767
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
buildah pull from registry.fedoraproject.org fails with error tls: unexpected message #1504
Comments
I was hitting this same problem earlier, but now it seems to work fine again. Could it have been an issue on the registry side that may have since been fixed? |
It smells like it. @mtrmac thoughts/opinions? |
Now, it is working for me as well without making any changes. Not sure where the problem was though ... Log from successful run:
Closing the issue becasue I no longer see this. |
I'm still seeing this, on a F30 Silverblue host. I wonder if it's something to do with Go and TLS certificate handling? |
Hmm, yeah, I can confirm that |
Per the above and IRC pings, I'm going to reopen. |
Just adding a IRC chat line that might help with debugging from rishi:
|
It was @sinnykumari who discovered that originally. It's part of her initial report but got a bit lost in the text. :) |
i'm having the exact same issue under silverblue 30. podman pull works, buildah pull fails with |
Can you try with the buildah from master? |
sorry for the late response, i was fighting with my local installation of silverblue 30...
so the latest master works for me. here is the output of buildah that comes currently with silverblue 30:
thanks |
I'm also seeing this error with buildah pulling from registry.fedoraproject.org on Fedora 30. It works if I downgrade, and it works if I upgrade to the buildah from rawhide.
|
Thanks for testing @carlwgeorge
If that's true, then it seems like a Fedora packaging bug to me:
|
Ah, I see.
This is an RPM ordering issue. The short term fix is to bump the F30 package to release 18 or higher. Long term, your suggestion of using |
There's an new build that unbreaks the update path: This issue can be closed now. |
This issue is fixed with buildah-1.7-18.git873f001.fc30.x86_64 in Fedora 30 |
Description
buildah pull fails while fetching image from registry.fedoraproject.org
buildah version - bbuildah-1.7-17.dev.git146a0fc.fc30.x86_64
System detail - Fedora 30 Silverblue
Full log:
Additional info:
Note that
podman pull registry.fedoraproject.org/fedora
andbuildah pull docker.io/fedora
seems to work fineThe text was updated successfully, but these errors were encountered: