FLAME Backend often stuck at "Pulling container image..."

How big is your image? The first time an image is pulled to a new host (different host from the parent ), it can take longer but shouldn’t be timing out like this unless we’re having issues with our registry. Can you try to configure the boot_timeout of the pool to something like 120_000 and see if fly is able to eventually pull the image? It will log how long the image pull took. I will check on our side to see if the registry in iad is acting up.

1 Like