-
Notifications
You must be signed in to change notification settings - Fork 330
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 Nix static build with wasmedge? #922
Comments
If I change nix as follows, the result crun will become dynamic. vi default-arm64.nix ./result/bin/crun --version file ./result/bin/crun |
Hi @Edingh , I don't think crun supports static binary with wasm support out of the box as of now.I think code would need a slight refactor since crun uses Since all the runtimes already ship static library i think it should not be too hard with a slight refactor but afaik its not on the roadmap yet so maybe we can keep issue open till we get more request for it ? |
we would need to statically build and link wasmedge as well, and not use |
Yes I think it would be a small refactor. I'll try checking this issue. |
I don't think it is a high priority issue that you should hurry to look at. Still it is not clear what are the advantages |
I would leave this to community. Quite often people say they want static and then they disappear. |
As you can see, docker release include static build runc binary; and it can run on Android and other linuxKernel-based OS. k3s (or even almost all k8s-related project) also released in static build binary. This way (static build binary), we can extend crun usage range. |
The way you recommended to static build using Nix does not include wasmedge support.
So how to Nix static build with wasmedge? Is it possible?
If it's possible, would you like to release the binary with wasmedge support?
Thanks for the hlep!
The text was updated successfully, but these errors were encountered: