spin: On arm64, I get "cannot allocate memory (os error 12)" on executing spin up command
This is regarding the quickstart from the docs.
It runs on my X86 laptops just fine. But on arm64 platforms such as Raspberry Pi 3 (1 gb ram) or Arm based EC2 instances(with 2 GB ram), spin build works without any issues but on spin up I get the following error:
Error: failed to create stack pool mapping
caused by:
0: mmap failed to allocate 0x7d3e8888 bytes
1: Cannot allocate memory (os error 12)
Am I low on ram ? do I need more for Arm ?
Image attached.
About this issue
- Original URL
- State: closed
- Created 3 years ago
- Comments: 16 (6 by maintainers)
Commits related to this issue
- Dynamically detect support for Wasmtime's pooling allocator This commit is intended to address #2119 and mirror bytecodealliance/wasmtime#8610. The base problem is that some systems are configured wi... — committed to alexcrichton/spin by alexcrichton 3 years ago
- Dynamically detect support for Wasmtime's pooling allocator This commit is intended to address #2119 and mirror bytecodealliance/wasmtime#8610. The base problem is that some systems are configured wi... — committed to alexcrichton/spin by alexcrichton 3 years ago
- Dynamically detect support for Wasmtime's pooling allocator This commit is intended to address #2119 and mirror bytecodealliance/wasmtime#8610. The base problem is that some systems are configured wi... — committed to calebschoepp/spin by alexcrichton 3 years ago
To validate an assumption here, could you test by passing the
--disable-poolingflag as well, please? (spin up --disable-pooling)Thanks!
This came up in https://github.com/bytecodealliance/wasmtime/issues/8607 and on the bytecodealliance Zulip and I think I got a fix for this in Wasmtime which I’ve ported over to Spin as well