-
Notifications
You must be signed in to change notification settings - Fork 2.4k
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
podman pull: can't talk to a V1 container registry #14864
Comments
Looks like a temporary fart on |
A friendly reminder that this issue had no activity for 30 days. |
@edsantiago, have you seen this flake again? |
Last seen July 14 on two tests, all at the same time: f35 rootless, f35 root. The common timestamp strongly indicates a problem on the registry. |
A friendly reminder that this issue had no activity for 30 days. |
@edsantiago any update? |
I think this is a flake on the registry rather than Podman. |
Ok I will close and hope it has gone away. |
Sorry for the late response. My (incomplete) logs do not show any instances since July 14. |
New flake in
int
test setup:log: https://api.cirrus-ci.com/v1/task/5147934521032704/logs/main.log
The text was updated successfully, but these errors were encountered: