Remote builder issues

Questions / Help
1

I’ve recently started having HEAPS of issues with my fly deploy --remote-only via Github Actions, that I assume stem from the size of my project.

I have a monorepo that deploys 3 apps via Github Actions on a commit to main:

/apps
/app1
fly.toml
Dockerfile
/app2
fly.toml
Dockerfile
/app3
fly.toml
Dockerfile

The dockerfiles all build successfully on their own locally, but fail almost 90% of the time through superfly/flyctl-actions@1.4

Commonly I will get the OOM email:

Hello! Your “fly-builder-green-shape-2875” application hosted on Fly.io crashed because it ran out of memory

The Dockerfile will also just be killed randomly mid-build, for example:

#10 55.37 Killed
#10 ERROR: executor failed running [/bin/sh -c yarn workspaces focus app1]: exit code: 137

I’ve got no clue where to start debugging this further, so any help would be appreciated!

Thought: Is the one builder handling all 3 remote app deployments at once? Could that be the issue?

2

As an additional thing, I just upgraded to the paid plan, reset my builder so it would move up to the 8GB provision, still ran out of memory :eyes::eyes::eyes::eyes::eyes:

3

This topic was automatically closed 7 days after the last reply. New replies are no longer allowed.