-
-
Notifications
You must be signed in to change notification settings - Fork 3.3k
Description
Description
Hi, I'm experimenting with Coolify - awesome project!
I ran into the following problem multiple times - therefore I thought its best I report it.
My best educated guess is that the Coolify just runs out of memory because my VPS hasn't got enough. 🤷 So I guess it's not a Coolify bug per se and I should just upgrade my VPS?
But for beginners (like me) it would a cool addition to have some information about it in the docs - maybe in a section called "Troubleshooting"?
My setup:
- VPS: Hetzner CPX11, vCPU: 2 (AMD), RAM: 2 GB
- 2 PHP projects with 1 mysql db each
- 1 SvelteKit (NodeJS) project
It seems that Coolify get's stuck on "npm ci" (via nixpacks), at least that's what I see last in the logs before Coolify becomes unresponsive. SSH connection to the server is still possible.
Restarting the server does not always help, in my latest tries the deployment gets stuck again.
Only if I stop one php project + one database, builds are possible again.
Minimal Reproduction (if possible, example repository)
VPS: Hetzner CPX11 vCPU 2 AMD RAM 2 GB
- Add 1 php project (laravel) + 2 mysql dbs, 1 sveltekit (nodejs) project
- Add new project with public GitHub repository https://github.com/mandrasch/ddev-craftcms-vite
- Switch port to 80
- Disable health checks
- Run Deploy --> nixpacks tries composer install (successful), but get's stuck at
npm ciand Coolify will become unresponsive
(For SvelteKit I documented my steps here:
https://dev.to/mandrasch/deploy-sveltekit-with-ssr-on-coolify-hetzner-vps-24c5)
Exception or Error
Full deployment log: https://gist.github.com/mandrasch/4896095a5f9fc1f75bd575896926db1b
Version
v4.0.0-beta.269
Happy to provide more data. Thanks very much for providing Coolify as Open Source! 🙏
Please feel free to close this if irrelevant / not the right place for this. Cheers!