-
Notifications
You must be signed in to change notification settings - Fork 137
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
Bug - Does Nanos support Mac OS M1? #2078
Comments
of course - you might get that msg if you are using a pkg that is x86 only on a (arm) m1 but for this one you shouldn't being seeing that msg
(eg: i see this for 20.0.0 but that's cause it is x86 only) if you want to run an x86 pkg on arm you'd do this:
|
Thanks for the help. I've attempted to resolve but got a few error messages after attempting to use node:v20.0.0 on an M1.
Seems like ops requires QEMU, or a Hypervisor. Is there an support for M1 without homebrew? Any steps on resolving would be great! |
you can install ops a handful of ways: through curl: https://ops.city/ (this is probably the easiest option for mac users) or as you mentioned you didn't want to use homebrew: https://github.com/nanovms/homebrew-ops but yes ops will need qemu to run locally, also - the 'eyberg/node:v20.0.0' as i mentioned earlier is x86 and that's why it's wanting to use that x86 kernel - |
Thanks for the helpful links.
I'll attempt to install via |
the desktop app packages both qemus but I just saw that it was only setting up aarch64 - w/the new update i just made it should have both in /usr/local/bin/qemu-system-aarch64 and /usr/local/bin/qemu-system-x86_64 most people would have this in their. path
but if not you can add it via (which is what the install script does):
you can also just do the |
I've attempted to use a nanovm and was unable to run command
ops pkg load eyberg/node:20.5.0
cli only returnspackage not found
.The text was updated successfully, but these errors were encountered: