-
Notifications
You must be signed in to change notification settings - Fork 15
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
How to pass options to shim? #115
Comments
I'll let @jsturtevant and/or other maintainers chime in re: generic wasmtime or spin runtime configurability but I did want to mention that there happens to be a recent PR in Spin relating to the specific use case mentioned above. See fermyon/spin#2508. The intention there is to not require any specific config for running properly in such environments as mentioned above (i.e. it should dynamically disable pooling) . When the shim bumps to the future Spin release with the aforementioned logic included, specific wasmtime/Spin config should no longer be necessary for this scenario. |
We don't have a story right now for passing configuration to the shim to configure the underlying runtime. Would spin's Potentially, we could do something with containerd/runwasi#573 but need some more design work on how to make that generic. |
@matsbror I think this issue is addressed in fermyon/spin#2508 specifically. The broader context for other config options that we would pass is still relevant though. |
My issue has been resolved so the issue can be closed, but I think there could be a need to pass config options to the shim, still. |
I also have a need to pass config options to the shim. Specifically I want to be able to set the environment variables As a SpinKube user I'd love to be able to set these values in my |
I need to run spin with the
--disable-pooling
option because my RISCV64 and Aarch64 boards only have 39 bit virtual addresses and thus cannot make the 6T mmap that Wasmtime pooling allocator makes. How can I pass that option to the shim?The text was updated successfully, but these errors were encountered: