New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Base Repo OOMs on Fly.io #170
Comments
I have attempted a paid plan, but without running machines I can't rescale the apps. I think starting over completely and choosing a higher configuration (multiple CPUs, 4GB RAM) may solve, but if that's the case it should be documented, and I'm not sure how that affects pricing on Fly.io. |
I had the same issue, managed to fix it by |
Yea, unfortunately mine was in a broken state where the app never successfully deployed, so I couldn't scale the memory for it and it was stuck at 256. Only solution was to delete the fly app and start over, choosing the 512 memory version to being. I think that is okay, but should be documented. |
Stuck on this as well... Is the memory update applicable to the DB machine or the website machine(staging/production)? My assumption is the DB but want to confirm before I blow something up EDIT: figured it out, its for the staging/prod website machines. |
I've had success by setting the following in [deploy]
release_command = "bash ./scripts/migrate.sh" and creating a script that looks like #!/bin/bash
fallocate -l 512M /swapfile
chmod 0600 /swapfile
mkswap /swapfile
echo 10 > /proc/sys/vm/swappiness
swapon /swapfile
echo 1 > /proc/sys/vm/overcommit_memory
npx prisma migrate deploy related: https://community.fly.io/t/prisma-sqlite-causes-an-out-of-memory-error-on-deploy/11039 |
@kwigley if you want to open a PR with those changes, i would gladly merge it :) |
hmm, I'm seeing OOM again on a fresh app:
|
Have you experienced this bug with the latest version of the template?
yes
Steps to Reproduce
Clone the repo and follow the README all the way through the Fly.io deployment steps.
For the Postgres create step, choose the Development - Single node, 1x shared CPU, 256MB RAM, 1GB disk configuration.
Link the DB to the app, etc.
When finally committing and pushing, the Deploy action fails with
exit code 137
.Expected Behavior
I would expect the base Blues Stack to be able to deploy on the Fly.io free tier, especially as it is heavily documented and encouraged in the docs.
Actual Behavior
Deploy fails with out of memory error.
The text was updated successfully, but these errors were encountered: