Unable to pull image

Questions / Help Build debugging
1

Hello,

I’m trying to deploy my app in the lhr region and it keeps hanging when pulling the image.

The app is called scrabble-score-e630

When trying a deploy using the flyci I’m not sure it’s even able to push the image, however via github actions it’s able to move past it.

Link to github actions: remove skyscanner artifactory · runmoore/scrabble-score@c6d6fe9 · GitHub

I’m very new to flyio so let me know if I need to provide any more information.

2022-04-15T12:50:01.229 runner[0c32b1fc] lhr [info] Starting instance
2022-04-15T12:50:01.967 runner[0c32b1fc] lhr [info] Configuring virtual machine
2022-04-15T12:50:01.969 runner[0c32b1fc] lhr [info] Pulling container image
2022-04-15T12:52:01.989 runner[0c32b1fc] lhr [info] Pull failed, retrying (attempt #0)
2022-04-15T12:54:02.010 runner[0c32b1fc] lhr [info] Pull failed, retrying (attempt #1)
2022-04-15T12:56:02.031 runner[0c32b1fc] lhr [info] Pull failed, retrying (attempt #2)
2022-04-15T12:56:02.031 runner[0c32b1fc] lhr [info] Pulling image failed
...
2022-04-15T12:56:49.943 runner[f6632c1d] lhr [info] Starting instance
2022-04-15T12:56:50.714 runner[f6632c1d] lhr [info] Configuring virtual machine
2022-04-15T12:56:50.716 runner[f6632c1d] lhr [info] Pulling container image
2022-04-15T12:58:50.736 runner[f6632c1d] lhr [info] Pull failed, retrying (attempt #0)
2022-04-15T13:00:50.760 runner[f6632c1d] lhr [info] Pull failed, retrying (attempt #1)
2022-04-15T13:02:50.782 runner[f6632c1d] lhr [info] Pull failed, retrying (attempt #2)
2022-04-15T13:02:50.782 runner[f6632c1d] lhr [info] Pulling image failed
2

I guess the first thing I’d check here would be to see if the image is actually pushed, as you say you’re not sure. Since if not, that would explain why the runner can’t subsequently pull it.

To put aside any possible issue with github actions (e.g its networking) do you have docker installed locally? If not, you could still use a remote builder, from the folder with the fly.toml in:

fly deploy
or
fly deploy --remote-only

Doing that you would see the output, as it happens. And you would be able to confirm if the image is indeed pushed (as you would watch it happen in real-time, with a progress bar and success/fail message).

Only you would then have a bit more information to help debug where the problem lies: whether it’s the github action (like, if the deploy does work when run locally), the app/image, or the registry push/pull.

3

Just popping in to mention we’ve just declared an incident with the registry. Investigating…

1 Like
4

Ah! Well that would explain it then. Thanks for the update.

@chrismoore Sounds like you should be able to simply retry once Fly sort that issue and it should then work

2 Likes
5

I’m experiencing the same thing since yesterday evening (CEST). Is it related to Fly.io Status - Intermittent API unavailability ?