Blues stack according to tutorial, fails on deploy, runs locally just fine. I have changed the app name, i.e. instead of fly apps create blues-stack-template I have replaced with ```
fly apps create my-own-name
relevant log section from github actions:
```shell
> Machine 148e2d15fe6589 has state: destroyed
> Waiting for 148e2d15fe6589 to get exit event
✖ release_command failed
Error release_command failed running on machine 148e2d15fe6589 with exit code 134.
Check its logs: here's the last 100 lines below, or run 'fly logs -i 148e2d15fe6589':
Pulling container image registry.fly.io/het-nederlands-staging:deployment-01HYZETNPPFP3ZHZ649NC42Y3P
✖ Failed: error release_command machine 148e2d15fe6589 exited with non-zero status of 134
Successfully prepared image registry.fly.io/het-nederlands-staging:deployment-01HYZETNPPFP3ZHZ649NC42Y3P (1.499804105s)
Configuring firecracker
2024-05-28T11:19:58.838494222 [01HYZEV91WBRHTMD8C7AVGH1AA:main] Running Firecracker v1.7.0
[ 0.037880] PCI: Fatal: No config space access function found
INFO Starting init (commit: d772ddd9)...
INFO Preparing to run: `docker-entrypoint.sh npx prisma migrate deploy` as root
INFO [fly api proxy] listening at /.fly/api
2024/05/28 11:19:59 INFO SSH listening listen_address=[fdaa:4:bee6:a7b:69:5e9:198:2]:22 dns_server=[fdaa::3]:53
Machine created and started in 2.954s
npm warn exec The following package was not found and will be installed: prisma@5.14.0
<--- Last few GCs --->
[328:0x5c768b0] 6929 ms: Scavenge (reduce) 253.5 (257.8) -> 253.4 (258.8) MB, 2.9 / 0.0 ms (average mu = 0.694, current mu = 0.621) allocation failure;
[328:0x5c768b0] 7037 ms: Mark-sweep (reduce) 254.3 (258.8) -> 254.0 (259.5) MB, 72.4 / 0.0 ms (+ 64.1 ms in 30 steps since start of marking, biggest step 11.9 ms, walltime since start of marking 178 ms) (average mu = 0.552, current mu = 0.356) alloca
<--- JS stacktrace --->
FATAL ERROR: Reached heap limit Allocation failed - JavaScript heap out of memory
1: 0xb9c310 node::Abort() [npm exec prisma migrate deploy]
2: 0xaa27ee [npm exec prisma migrate deploy]
3: 0xd73eb0 v8::Utils::ReportOOMFailure(v8::internal::Isolate*, char const*, bool) [npm exec prisma migrate deploy]
4: 0xd74257 v8::internal::V8::FatalProcessOutOfMemory(v8::internal::Isolate*, char const*, bool) [npm exec prisma migrate deploy]
5: 0xf515d5 [npm exec prisma migrate deploy]
6: 0xf63aad v8::internal::Heap::CollectGarbage(v8::internal::AllocationSpace, v8::internal::GarbageCollectionReason, v8::GCCallbackFlags) [npm exec prisma migrate deploy]
7: 0xf3e19e v8::internal::HeapAllocator::AllocateRawWithLightRetrySlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [npm exec prisma migrate deploy]
8: 0xf3f567 v8::internal::HeapAllocator::AllocateRawWithRetryOrFailSlowPath(int, v8::internal::AllocationType, v8::internal::AllocationOrigin, v8::internal::AllocationAlignment) [npm exec prisma migrate deploy]
9: 0xf1ff92 v8::internal::Factory::AllocateRawWithAllocationSite(v8::internal::Handle<v8::internal::Map>, v8::internal::AllocationType, v8::internal::Handle<v8::internal::AllocationSite>) [npm exec prisma migrate deploy]
10: 0xf2a7ec v8::internal::Factory::NewJSObjectFromMap(v8::internal::Handle<v8::internal::Map>, v8::internal::AllocationType, v8::internal::Handle<v8::internal::AllocationSite>) [npm exec prisma migrate deploy]
11: 0x1059d85 v8::internal::JsonParser<unsigned short>::BuildJsonObject(v8::internal::JsonParser<unsigned short>::JsonContinuation const&, v8::base::SmallVector<v8::internal::JsonProperty, 16ul, std::allocator<v8::internal::JsonProperty> > const&, v8::internal::Handle<v8::internal::Map>) [npm exec prisma migrate deploy]
12: 0x105ba08 v8::internal::JsonParser<unsigned short>::ParseJsonValue() [npm exec prisma migrate deploy]
13: 0x105c11f v8::internal::JsonParser<unsigned short>::ParseJson() [npm exec prisma migrate deploy]
14: 0xdf9913 v8::internal::Builtin_JsonParse(int, unsigned long*, v8::internal::Isolate*) [npm exec prisma migrate deploy]
15: 0x17126f9 [npm exec prisma migrate deploy]
INFO Main child exited with signal (with signal 'SIGABRT', core dumped? false)
INFO Starting clean up.
WARN could not unmount /rootfs: EINVAL: Invalid argument
[ 8.336873] reboot: Restarting system
machine restart policy set to 'no', not restarting
Checking DNS configuration for het-nederlands-staging.fly.dev
Error: release command failed - aborting deployment. error release_command machine 148e2d15fe6589 exited with non-zero status of 134
Error: Process completed with exit code 1.