@jugorocks may I hijack your app and attempt to deploy to it ?
My first attempt is going to be create a new app in the same org, then redeploy the same image it is in use (so your app doesn’t change)
‘hijack’ sounds thrilling, but sure let’s play. what’s my move from here?
and i don’t know if i have an org… it’s personal thing. i mean … idk
Let’s try to reproduce in another app and same org (yes, it is your personal org)
First create the app with:
fly apps create readway-staging -o personal
and then attempt to deploy:
fly deploy -a readway-staging
it reproduces the error
this went down and it used previously made image, only updated it with 100Kb context.
deployed and running.
upd: thnx for the tip. i though about making a betta (coz it’s betta than alpha, but bugs)) version of the app for testing, and i thought i’d need to make a new repo for it. now i can do this ‘deploy to the other app’ trick. which makes it easier to not loose my mind in the codes. thnx
1 Like
Interesting. does the main app still fails? can you post the fly deploy output for “readway” app?
main went down as well now. it’s all working. like magic.
context transfer was 2.57Kb.
wanna see the logs tho?
No need, happy it went through but not so happy because I have no repro hah
I appreciate your help @jugorocks ! let me know if it happens again please.
1 Like
ok. writing to you if something goes wrong)
why no repo? don’t you have a crazy idea in mind?
I’m having the same issue here. I can’t deploy my application. I tried destroying the builder but that doesn’t help. Any ideas?
--> Verified app config
Validating ./apps/***-web/fly.toml
Platform: machines
✓ Configuration is valid
==> Building image
WARN Failed to start remote builder heartbeat: Not authorized to access this firecrackerapp
Waiting for remote builder fly-builder-throbbing-sky-256...
Error: failed to fetch an image or build from source: error connecting to docker: failed building options: failed probing "***-730": context deadline exceeded
Error: Process completed with exit code 1.
1 Like
I mean, I have no reproducible way to debug the problem because the deploy to staging and main app succeeded
hi @mxs2019! I saw your premium support request. I’ll follow up there. thanks
Did you find any alternative? I had many problems with deploy today (again) and because of it my production app was down for some time… I will be grateful for a good alternative
I am still facing the same error. Tried it on both fra and den region. Deleting the builders did not help.
flyctl deploy --remote-only
==> Verifying app config
Validating /my/project/folder/fly.toml
Platform: machines
✓ Configuration is valid
--> Verified app config
==> Building image
WARN Failed to start remote builder heartbeat: server returned a non-200 status code: 504
WARN Remote builder did not start in time. Check remote builder logs with `flyctl logs -a fly-builder-aged-fire-5503`
Error: failed to fetch an image or build from source: error connecting to docker: remote builder app unavailable
The mentioned remote builder logs:
2023-10-30T13:02:53Z runner[4d89136ec17798] fra [info]Pulling container image docker-hub-mirror.fly.io/flyio/rchab:sha-a4467b8
2023-10-30T13:02:54Z runner[4d89136ec17798] fra [info]Successfully prepared image docker-hub-mirror.fly.io/flyio/rchab:sha-a4467b8 (788.917509ms)
EDIT:
For some reason, about 21 minutes after I gave up trying the builder woke up and started working:
2023-10-30T13:02:53Z runner[4d89136ec17798] fra [info]Pulling container image docker-hub-mirror.fly.io/flyio/rchab:sha-a4467b8
2023-10-30T13:02:54Z runner[4d89136ec17798] fra [info]Successfully prepared image docker-hub-mirror.fly.io/flyio/rchab:sha-a4467b8 (788.917509ms)
2023-10-30T13:23:59Z runner[4d89136ec17798] fra [info]Setting up volume 'machine_data'
2023-10-30T13:23:59Z runner[4d89136ec17798] fra [info]Uninitialized volume 'machine_data', initializing...
2023-10-30T13:23:59Z runner[4d89136ec17798] fra [info]Encrypting volume
2023-10-30T13:24:06Z runner[4d89136ec17798] fra [info]Opening encrypted volume
2023-10-30T13:24:08Z runner[4d89136ec17798] fra [info]Formatting volume
2023-10-30T13:24:08Z runner[4d89136ec17798] fra [info]Configuring firecracker
2023-10-30T13:24:09Z app[4d89136ec17798] fra [info][ 0.210907] PCI: Fatal: No config space access function found
2023-10-30T13:24:09Z app[4d89136ec17798] fra [info] INFO Starting init (commit: 15238e9)...
2023-10-30T13:24:09Z app[4d89136ec17798] fra [info] INFO Mounting /dev/vdb at /data w/ uid: 0, gid: 0 and chmod 0755
2023-10-30T13:24:09Z app[4d89136ec17798] fra [info] INFO Resized /data to 53670313984 bytes
2023-10-30T13:24:09Z app[4d89136ec17798] fra [info] INFO Preparing to run: `./entrypoint ./dockerproxy` as root
2023-10-30T13:24:09Z app[4d89136ec17798] fra [info] INFO [fly api proxy] listening at /.fly/api
....
....
After I noticed that a fly deploy worked.
EDIT2:
Its broken again.
Seems I hit the same problem: my gitlab CI, which just worked for a long time now, fails.
any idea what I could do?
$ flyctl deploy
==> Verifying app config
Validating /builds/hands-development/swedencpp/snow/fly.toml
Platform: machines
✓ Configuration is valid
--> Verified app config
==> Building image
WARN Failed to start remote builder heartbeat: server returned a non-200 status code: 500
Error: failed to fetch an image or build from source: server returned a non-200 status code: 500
Cleaning up project directory and file based variables
00:00
ERROR: Job failed: exit code 1
–edit: Just see that I have a status error on my dashboard, seem some internal problems on fly.io
oi, proceeded a bit, but now the page is offline, after this failure
(the previous error was better, since it at least kept the old version online)
Updating existing machines in 'swedencpp' with rolling strategy
> Updating e28650e0f67458 [app]
> Updating e28650e0f67458 [app]
✖ Machine e28650e0f67458 [app] update failed: failed to update VM e28650e0f67458: request returned non-2xx status, 504
Error: failed to update VM e28650e0f67458: request returned non-2xx status, 504 (Request ID: 01HE0DVG84ZB2QEYWCQDX8CFER-iad)
Cleaning up project directory and file based variables
00:01
ERROR: Job failed: exit code 1
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.