Hi, I’ve created a new staging app for my repo and I’m getting this error. same repo on a different app was deployed with no issues. trying to create a third app also yields with same error code.
there are no logs
Hi, I’ve created a new staging app for my repo and I’m getting this error. same repo on a different app was deployed with no issues. trying to create a third app also yields with same error code.
there are no logs
Looks like I’m getting the same issue
--> Building image done
==> Pushing image to fly
The push refers to repository [registry.fly.io/osc-studio-test]
d6ee529b9904: Layer already exists
fc8b78fe5de6: Layer already exists
f77d9f2c3711: Layer already exists
60f30a4a88fc: Layer already exists
ffc4bcc74a16: Layer already exists
c779ccd54308: Layer already exists
dcf66e33b809: Layer already exists
742b71d69c35: Layer already exists
461160bf3157: Layer already exists
e90e84f50ac8: Layer already exists
fe7b1e9bf792: Layer already exists
deployment-01GFN3GNTGRKAH4SNRMFADEPFR: digest: sha256:9059dfc40c1939c72f1e8296b32febb13c8b8e38c1a9549d16d748a9d0fb27b6 size: 2626
--> Pushing image done
Image: registry.fly.io/osc-studio-test:deployment-01GFN3GNTGRKAH4SNRMFADEPFR
Image size: 571 MB
==> Creating release
Error You hit a Fly API error with request ID: 01GFN3GWBEJQ3ZFQ5BDB2HDFG3-lhr
Just chiming in to follow this thread
==> Creating release
Error You hit a Fly API error with request ID: 01GFN45450KSVZJZRY7TVYJ1ST-fra
And this is the verbose output. https://status.flyio.net doesn’t seem to report anything regarding this yet.
I see the same issue. I get the error on an app I created today. Same repo on an older app works.
EDIT: I was able to fix this by manually scaling the app: fly scale count
Awesome, that worked for me too. Cheers!
same issue
==> Creating release
Error You hit a Fly API error with request ID: 01GFNB36M08JZZRB8TV6K6YQA2-fra
i try:
flyctl version update
flyctl agent restart
and
==> Creating release
--> release v2 created
--> You can detach the terminal anytime without stopping the deployment
==> Monitoring deployment
1 desired, 1 placed, 1 healthy, 0 unhealthy
--> v0 deployed successfully
it works!!!