S C:\Users\danie\OneDrive\Skrivebord\Secrets\Hay Day discord> flyctl deploy
==> Verifying app config
Validating C:\Users\danie\OneDrive\Skrivebord\Secrets\Hay Day discord\fly.toml
✓ Configuration is valid
→ Verified app config
==> Building image
Waiting for remote builder fly-builder-young-sun-972…
Waiting for remote builder fly-builder-young-sun-972…
Waiting for remote builder fly-builder-young-sun-972…
Waiting for remote builder fly-builder-young-sun-972…
Waiting for remote builder fly-builder-young-sun-972…
Waiting for remote builder fly-builder-young-sun-972…
Waiting for remote builder fly-builder-young-sun-972…
Remote builder fly-builder-young-sun-972 ready
Waiting for remote builder fly-builder-young-sun-972…
Waiting for remote builder fly-builder-young-sun-972…
Waiting for remote builder fly-builder-young-sun-972…
Waiting for remote builder fly-builder-young-sun-972…
Waiting for remote builder fly-builder-young-sun-972…
Waiting for remote builder fly-builder-young-sun-972…
Remote builder fly-builder-young-sun-972 ready
==> Building image with Docker
→ docker host: 24.0.7 linux x86_64
[+] Building 0.8s (10/10) FINISHED
=> [internal] load .dockerignore 0.1s
=> => transferring context: 2B 0.1s
=> [internal] load build definition from Dockerfile 0.1s
=> => transferring dockerfile: 168B 0.1s
=> [internal] load metadata for Docker 0.6s
=> [1/5] FROM Docker 0.0s
=> [internal] load build context 0.1s
=> => transferring context: 1.89kB 0.1s
=> CACHED [2/5] WORKDIR /bot 0.0s
=> CACHED [3/5] COPY requirements.txt /bot/ 0.0s
=> CACHED [4/5] RUN pip install -r requirements.txt 0.0s
=> [5/5] COPY . /bot 0.0s
=> exporting to image 0.0s
=> => exporting layers 0.0s
=> => writing image sha256:f79695b3e6d19c9fbb0471ef06ed27845fe7587cbf23a004d6881fe9418bc583 0.0s
=> => naming to registry.fly.io/haydayserver:deployment-01HXF835FD77B16GF0CZHYX6CT 0.0s
→ Building image done
==> Pushing image to fly
The push refers to repository [registry.fly.io/haydayserver]
857a5d478073: Pushed
7077e81270c5: Pushing [==> ] 15.28MB/257.1MB
I never had issues deploying before, hope anyone can help
Maybe this is still not fully resolved?
My CircleCI job is failing so not just my local network
Came here to post the same question. I have this problem too.
I’m a member of multiple organizations
- tried deploying to different organizations
- tried deploying to different regions
- tried building with the
--remote-onlyflag
Nothing works.
I have the same issue. it ends on
failed to fetch an image or build from source: error rendering push status stream: unexpected EOF
Yep, same issue here since 2 days (!!)
Same issue here, this started with this incident but never resolved for me: Fly.io Status - Users are unable to deploy their apps.
I’m deploying to ams local-only doesn’t do the trick for me either.
Mine sometimes ends with the same @theurerjohn3 posted or with the following:
WARN failed to finish build in graphql: Post "https://api.fly.io/graphql": context canceled
Full output:
==> Pushing image to fly
The push refers to repository [registry.fly.io/dnspager]
3613355e52e6: Pushed
b57b9134f7c2: Pushed
39eba04a5a42: Pushing 20.46MB/40.91MB
d2ccd2a10a6d: Pushing 36.43MB/167.2MB
9a25a3072d9b: Pushing 67.18MB/129MB
5f70bf18a086: Layer already exists
ee159245cccd: Pushed
a1a1b1105dc6: Pushed
f3cdf07b301c: Pushed
63e8ab389a92: Pushed
ab0464a79688: Pushed
095b79626589: Pushing 30.65MB/241.6MB
93dd400c4c3e: Pushed
36cc9c717032: Pushed
ddad9c31132c: Pushed
e0a9f5911802: Pushing 49.08MB/77.86MB
^C
WARN failed to finish build in graphql: Post "https://api.fly.io/graphql": context canceled
Fails for me in Amsterdam as well (didnt try anywhere else). Is there any way to pick a different builder location? Couldnt find it in fly deploy --help
Same for me, also in the Amsterdam Region.
I am pushing to bos, and having this issue.
We’re seeing similar issues in dfw across multiple apps - stuck on pushing to the registry.
We’re having the same problem in lhr.
Yep, same here using region ‘waw’
Stuck here even after going through all of the online suggestions.
==> Pushing image to fly
The push refers to repository [registry.fly.io/mkumm-blog]
bb92cea5218f: Pushing [====================================> ] 15.64MB/21.17MB
Same issue here
5f70bf18a086: Layer already exists
65253dd94090: Pushing 25.04MB/611.3MB
24a61b4f538a: Pushed
Wrote in to support about this and haven’t heard in 30 minutes, no status page update either.
Every single one of our downtime incidents in the past 2 weeks has been caused by Fly 
Yup. Same here. But somehow everyone’s problem is “machine specific” and localized. No need for any broader status communication, RCAs, apologies for constants interruptions over multiple days. Nope.
Hey folks. Sorry, I think it was my bad PR to fly-proxy. I’ve just rolled it back everywhere. Are you still seeing the problem?
I can confirm that the deployments went through. But I am seriously considering moving out of fly.
Have had multiple downtimes in the past week.
My deploy worked - thanks for the update!