flyctl machine run startup gets stuck at "Unpacking image"

Questions / Help
1

I’ve tried dfw and iad regions, in both a flyctl machine run . gets stuck unpacking the container image. This used to work just hours earlier.

flyctl output:

234faf3199f5: Layer already exists
7cd52847ad77: Layer already exists
deployment-01GVKDTYGMHMMGFJPTQFHRHQ2J: digest: sha256:91197542bf037a807a40fedd493924284d1cd1b4fb14e477322b166390c7f061 size: 3657
--> Pushing image done
Image: registry.fly.io/blahblah:deployment-01GVKDTYGMHMMGFJPTQFHRHQ2J
Image size: 131 MB

Success! A machine has been successfully launched in app blahblah, waiting for it to be started
 Machine ID: 91857709a96483
 Instance ID: 01GVKDV8QYTCVMTAQD2H5QMF58
 State: created

 Attempting to start machine...

Error machine failed to reach desired start state, and restart policy was set to no restart

In logs I see

2023-03-15T19:51:48Z runner[4d891156f61398] dfw [info]Pulling container image registry.fly.io/blahblah:deployment-01GVKD813YDMQJ123DMPEP5S61
2023-03-15T19:51:49Z runner[4d891156f61398] dfw [info]Unpacking image
2

Maybe this is due to the Consul cluster outage: Fly.io Status - Consul cluster outage

3

It seems this has recovered, so it probably was the Consul outage.

4

If this machine has secrets, it was probably failing to pull those from vault during yesterday’s outage. We could put these in logs explicitly.

5

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