2:10 p.m.
I'm sorry I'm not an expert on these things, but nobody else has
replied. I would offer that most likely, there's a CDN providing those
downloads. Since the problem only happened recently for you, perhaps
it's the result of some temporary outage.
I don't know the options off-hand, but I'm pretty certain there's a way
to feed a user-supplied image to podman machine init. Assuming so, you
could perform the download from a different network / location, and
transfer the file as needed. I realize it's a PITA, but may be more
reliable for the short-term.
Hopefully the situation is/will clear up shortly. Please do let us know
if not.
---
Chris Evich (he/him), RHCA III
Senior Quality Assurance Engineer
If there's a "hard-way", I'm the first one to implement it.
On 6/30/23 12:18, Mehdi Haghgoo via Podman wrote:
Hi,
I have started to have problems recently downloading coreos images when initializing
podman machine (via terminal or Podman Desktop) on macOS.
Here are the errors:
mhd@MacBook ~ % podman machine init
Error: Get "https://builds.coreos.fedoraproject.org/streams/testing.json": read
tcp 192.168.1.109:54792->18.64.141.56:443: read: connection reset by peer
Is there a way I can set a mirror repository (if there is such a mirror) for coreos to
download its image from?