WARN Failed to start remote builder heartbeat: You hit a Fly API error with request ID: 01GM8HNNMKZK8QA2XPR8Z4FZ7S-iad
Error failed to fetch an image or build from source: error connecting to docker: You hit a Fly API error with request ID: 01GM8HPBNQQBNTSXQDMQ065DMM-iad
Searching for this type of error it seems to usually be deployment issues with the infrastructure.
Noticed there were issues yesterday, are there some new ones today?
We’re seeing deployment issues across multiple apps again. They’re getting stuck on “Starting instance” in the logs, with the instance’s status stuck on “pending”. Redeploying and restarting doesn’t help, and there’s no log output coming from the applications. (This is in ORD now, not IAD.)
I’m having a bunch of problems deploying (to an app in ewr) now as well. I’ve tried remote but am seeing this:
WARN Failed to start remote builder heartbeat: Couldn’t allocate volume, no disks available (region: atl, size_gb: 50)
Error failed to fetch an image or build from source: Couldn’t allocate volume, no disks available (region: atl, size_gb: 50)
@discoursebum yes all fixed! We brought a new Atlanta region online today, but it’s not fully enabled. We had an Atlanta region a few years ago and killed it off, but there were some DB records that suggested a person connection through Atlanta could get disks for a builder there. The DB was lying, so I deleted it.
Error failed to fetch an image or build from source: error building: error during connect: Post "http://[fdaa:1:651a:a7b:c207:2f74:89a:2]:2375/v1.41/build?buildargs=null&buildid=upload-request%3A5ac16aa6c7e6bc4ca96191e48cda2dc6c3006289f1ffd10f9bf0bb422d2783ef&cachefrom=null&cgroupparent=&cpuperiod=0&cpuquota=0&cpusetcpus=&cpusetmems=&cpushares=0&dockerfile=&labels=null&memory=0&memswap=0&networkmode=&rm=0&shmsize=0&target=&ulimits=null&version=2": EOF