Hey, thanks for helping me out.
No, it doesn’t work.
“set” sounds more like a command to set general windows operating system environmental variables.
Yes, that’s what you want. Passing via --env will set an environment variable in the builder. But we’re trying to tell flyctl where to create the builder, so the point is to set an environment variable on the the machine which is running flyctl, i.e. your computer.
2 Likes
$env:FLY_REMOTE_BUILDER_REGION=“iad”; fly deploy
made it! finally. Thanks a lot man, very appreciated.
2 Likes
hey! I’ve updated the CLI to v0.2.51. Tried to push the update with FLY_REMOTE_BUILDER_REGION=iad but my push is still hanging. The builders that were mentioned here I am not aware of. In the list of apps, I only see my apps, nothing related to builder, and nothing is suspended.
1 Like
For everyone stuck here, deploying using fly deploy --local-only worked for me since this bypasses fly remote builders. You have to have docker installed and running on your local machine though.
Hey @dangra, our app “segmetric-prod” has been down for 2 days already. Scaling up/down doesn’t work, can you help?
Your app is running in a single machine. Its host went under maintenance due to a hardware failure. Either you wait until the maintenance is done or try to scale it up.
Yesterday I managed to deploy without hanging issues by creating a builder of a different region as you suggested. But now, my deployed app hosted on a single machine keeps restarting and I am unable to reach it. I’m not understanding why.
Instead, an old machine I created 7 month ago is working perfectly (code, app & toml is the same). Any suggestion?
Your app is failing to start because of a shell script problem with your image’s entrypoint
eINFO Preparing to run:
/app/docker-entrypoint npm run startas root
/bin/bash: -
: invalid option
eINFO Main child exited normally with code: 1
see its logs with fly logs command.
As I wrote, scaling up doesn’t work. The new machine is restarted 10 times and then killed.
Your app is running out of memory - you can see this by running fly logs -a segmetric-prod. Use fly scale memory [memoryMB] to increase the machine’s memory.
2 Likes
Thank you, that worked. I assumed that when I used “fly scale” command the created instance would have the same resources as the original one, but that was not the case (which was surprising).
@bartblast Are your desired resource allocations specified in your fly.toml file?
No, it’s not specified in fly.toml (I was not aware of that), but in my opinion that is the expected behaviour.
This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.