Region Frankfurt cannot pull images

Default golang image cannot pull, and neither can docker.io-images.

@runar-rkmedia Hey there,

I just wanted to check-in and see if this is still an issue? If so, would you be able to provide me with an App name so I can dig in a bit further?

Hello @shaun ,

I also started facing this issue. Please find the below information about the app.

App: cookie3-app-staging

Logs:

Waiting for remote builder fly-builder-silent-breeze-1671...
Error failed to fetch an image or build from source: error connecting to docker: remote builder app unavailable
WARN Remote builder did not start in time. Check remote builder logs with `flyctl logs -a fly-builder-silent-breeze-1671`

Below are the builder logs:

2022-08-31T05:33:12Z runner[73d8d9d1a07d89] sjc [info]machine did not have a restart policy, defaulting to restart
2022-08-31T05:33:41Z runner[73d8d9d1a07d89] sjc [info]machine did not have a restart policy, defaulting to restart
2022-08-31T05:33:53Z runner[73d8d9d1a07d89] sjc [info]machine did not have a restart policy, defaulting to restart
2022-08-31T05:34:20Z runner[73d8d9d1a07d89] sjc [info]machine has reached its max restart count (10)

It looks like the builder app is crashing. Can you run the log tail in another window, then try deploying again? That should show what’s causing it to crash.

@jsierles
You mean running the logs for fly-builder-silent-breeze-1671 builder app, right?

It’s same as I posted earlier

2022-09-01T05:04:04Z runner[73d8d9d1a07d89] sjc [info]machine did not have a restart policy, defaulting to restart
2022-09-01T05:04:32Z runner[73d8d9d1a07d89] sjc [info]machine did not have a restart policy, defaulting to restart
2022-09-01T05:04:42Z runner[73d8d9d1a07d89] sjc [info]machine did not have a restart policy, defaulting to restart
2022-09-01T05:05:09Z runner[73d8d9d1a07d89] sjc [info]machine did not have a restart policy, defaulting to restart
2022-09-01T05:05:36Z runner[73d8d9d1a07d89] sjc [info]machine did not have a restart policy, defaulting to restart
2022-09-01T05:06:07Z runner[73d8d9d1a07d89] sjc [info]machine did not have a restart policy, defaulting to restart
2022-09-01T05:06:30Z runner[73d8d9d1a07d89] sjc [info]machine did not have a restart policy, defaulting to restart
2022-09-01T05:07:01Z runner[73d8d9d1a07d89] sjc [info]machine did not have a restart policy, defaulting to restart

One thing you can check is if the disk is full. In that case, you will need to remove the builder app and allow a new one to be created.

To check if the disk is full, go into your Fly dashboard for this app. On the Metrics page, you should see a link to “Open in Grafana” at the top right. In there, look for the volumes tab. That should show you volume usage.

1 Like

Yupp, that was the issue. The volume was full for the builder.

It worked after I deleted the builder app.

Thanks a lot for your support, and having grafana dashboards is really helpful for the apps. Kudos :tada:

1 Like