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

podman pull: can't talk to a V1 container registry #14864

Closed
edsantiago opened this issue Jul 8, 2022 · 9 comments
Closed

podman pull: can't talk to a V1 container registry #14864

edsantiago opened this issue Jul 8, 2022 · 9 comments
Labels
flakes Flakes from Continuous Integration locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@edsantiago
Copy link
Member

New flake in int test setup:

Running: podman [options] pull registry.access.redhat.com/ubi8-init
Trying to pull registry.access.redhat.com/ubi8-init:latest...
time="2022-07-07T18:22:15-05:00" level=warning msg="Failed, retrying in 1s ... (1/3). Error: copying system image from manifest list: determining manifest MIME type for docker://registry.access.redhat.com/ubi8-init:latest: Get \"https://registry.access.redhat.com/v2/ubi8-init/manifests/sha256:aaa17f9f2c8c628601688a830df297bf3548236efd7095b6448247bd759aed50\": net/http: TLS handshake timeout"
Error: initializing source docker://registry.access.redhat.com/ubi8-init:latest: can't talk to a V1 container registry

log: https://api.cirrus-ci.com/v1/task/5147934521032704/logs/main.log

@edsantiago edsantiago added the flakes Flakes from Continuous Integration label Jul 8, 2022
@vrothberg
Copy link
Member

Looks like a temporary fart on registry.access.redhat.com.

@github-actions
Copy link

github-actions bot commented Aug 8, 2022

A friendly reminder that this issue had no activity for 30 days.

@vrothberg
Copy link
Member

@edsantiago, have you seen this flake again?

@edsantiago
Copy link
Member Author

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.

@github-actions
Copy link

github-actions bot commented Sep 8, 2022

A friendly reminder that this issue had no activity for 30 days.

@rhatdan
Copy link
Member

rhatdan commented Sep 9, 2022

@edsantiago any update?

@vrothberg
Copy link
Member

I think this is a flake on the registry rather than Podman.

@rhatdan
Copy link
Member

rhatdan commented Sep 12, 2022

Ok I will close and hope it has gone away.

@rhatdan rhatdan closed this as completed Sep 12, 2022
@edsantiago
Copy link
Member Author

Sorry for the late response. My (incomplete) logs do not show any instances since July 14.

@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 16, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 16, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
flakes Flakes from Continuous Integration locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

No branches or pull requests

3 participants