Error: failed to fetch an image or build from source and ping gateway no response

Questions / Help
1 
➜  av git:(main) ✗ fly deploy
==> Verifying app config
Validating /Users/.../.../av/fly.toml
Platform: machines
✓ Configuration is valid
--> Verified app config
==> Building image
WARN Failed to start remote builder heartbeat: failed building options: failed probing "personal": context deadline exceeded

Error: failed to fetch an image or build from source: error connecting to docker: failed building options: failed probing "personal": context deadline exceeded

Testing authentication token… PASSED
Testing flyctl agent… PASSED
Testing local Docker instance… Nope
Pinging WireGuard gateway (give us a sec)… FAILED
(Error: ping gateway: no response from gateway received)

2

my toml

# fly.toml app configuration file generated for av on 2023-06-13T14:37:21-06:00
#
# See https://fly.io/docs/reference/configuration/ for information about how to use this file.
#

app = "av"
primary_region = "dfw"
kill_signal = "SIGINT"
kill_timeout = "5s"

[experimental]
auto_rollback = true
enable_consul = true
allowed_public_ports = []

[deploy]
release_command = "bash ./scripts/migrate.sh"


[mounts]
source = "av"
destination = "/data"


[env]
FLY_REGION = "dfw"
METRICS_PORT = "8081"
PORT = "8080"
PRIMARY_REGION = "dfw"

[[services]]
# http_checks = []
script_checks = []
protocol = "tcp"
internal_port = 8080
processes = ["app"]

[[services.ports]]
port = 80
handlers = ["http"]
force_https = true

[[services.ports]]
port = 443
handlers = ["tls", "http"]

[services.concurrency]
type = "connections"
hard_limit = 150
soft_limit = 100

[[services.tcp_checks]]
interval = "15s"
timeout = "4s"
grace_period = "15s"
restart_limit = 0

[[services.http_checks]]
interval = "10s"
timeout = "4s"
grace_period = "5s"
method = "get"
path = "/healthcheck"
protocol = "http"
tls_skip_verify = false
headers = {}
# [services.http_checks.headers]

[metrics]
port = 8081
path = "/metrics"
3

I’m also seeing this.

I thought it could be related to this incident but it has been marked as resolved?

WARN Failed to start remote builder heartbeat: failed building options: failed probing “personal”: context deadline exceeded

Error: failed to fetch an image or build from source: error connecting to docker: failed building options: failed probing “personal”: context deadline exceeded

Edit:

Seems to be working now!

4

I’m also still seeing this error:

Error: failed to fetch an image or build from source: error connecting to docker: failed building options: failed probing “”: context deadline exceeded

5

Still dont work.

6

I’m also seeing errors related to the docker registry.

...
a22b302686c4: Retrying in 3 seconds
a22b302686c4: Retrying in 2 seconds
a22b302686c4: Retrying in 1 second
Error: failed to fetch an image or build from source: error rendering push status stream: received unexpected HTTP status: 500 Internal Server Error
Error: Process completed with exit code 1.
1 Like
7

Still seeing this error. Edit: started working again (at least once) at 10:27 EST!

8

At the risk of going me too… Me too.

First noticed it on GHA then it was really slow to push from cloudbuild and my laptop.

9

Hello there,

I had this trouble yesterday and today I was able to fix it. Just run fly auth logout and then fly auth login. This works for me.

1 Like
10

I’m getting the error again.

The Docker build is extremely slow and after about 90 seconds I get:

Error: failed to fetch an image or build from source: error building: failed to solve: rpc error: code = Canceled desc = grpc: the client connection is closing

Edit:

While we investigate and fix the issue with our primary registry, users can temporarily deploy to our alternate registry using the
FLY_REGISTRY_HOST=registry2.fly.io fly deploy
command.

Edit:

Getting the same error when deploying with FLY_REGISTRY_HOST=registry2.fly.io fly deploy.

Edit:

I was able to deploy to the alternate registry :tada:

11

Just run fly auth logout and then fly auth login . This works for me.

Surprisingly, this worked for me which is kind of disappointing. I’d almost rather this be an outage on fly’s end than find out that doing voodoo like logging out/in might help.

1 Like
12

I was frustrated all day with the inability to deploy to either registry and the logout and login method fixed it. ¯_(ツ)_/¯

I’m good to go now.

13

Thank you! I was getting the failed probing "personal": context deadline exceeded on anything that required WireGuard. This worked for me to fix it!

1 Like
14

From here i am seeing “DOCKER…NOPE”>> I had same issues, I had to “Install Docker Locally”. And it marked “PASSED” when i checked “Fly Doctor” again.

1 Like
15

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.