-
Notifications
You must be signed in to change notification settings - Fork 58
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
ARM compatible image #965
Comments
It seems that a workaround solution could be to set |
this didn't work for me |
Unfortunately I don't have such platform to test it. Perhaps you could share the error you get ? The other solution might be the full virtualization where you could start a compatible system then start Monocle. |
No specific logs on the errors. Message I get during the launch:
And in the logs:
|
Same issue here so a +1 from me. M1 Mac user I'm going to try and work on alternatives, maybe just host in AWS as the product looks like what I need. same results and no logs to speak of. |
I succeeded to make it work by
|
@charlesdg can you post your setup in PR or something? |
Found a solution by running Docker Desktop with Rosetta enabled (had the first idea from ChatGPT). |
+1 to using Rosetta in Docker Desktop — this unblocked me |
I managed to run Monocle on M1 Mac using the tips above:
|
Where would I set |
@MisterJimson you can run it in your terminal session before starting monocle ( |
This is an x86 specific project... The flake calls out x86 in the devShell, and the upstream container has x86 binaries... when I try to start this in an Arm env, I get:
If you're on Linux and don't have Rosetta, another option might be, for those with KVM, is docker with QEMU, but otherwise, even building the container will take some work on Arm. |
Note that running monocle from source should work on ARM (see the toolchain supported platforms here). With cabal and ghc, you can follow https://github.com/change-metrics/monocle/blob/master/CONTRIBUTING.md#build-using-cabal |
Users relying on new Mac books are unable to run the Monocle compose. Indeed the Monocle container image is only compatible with x86_64 / amd64 architecture.
This issue is the place to discuss solutions such as:
The text was updated successfully, but these errors were encountered: