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
Pyre fails to run in Docker container on m1 host #744
Comments
|
When will there be progress? |
Sorry, this totally fell off my radar. Let me bring this back up to the team and see what they think. In the meantime, we released a new version of Pyre, so try updating to that and let me know if it helps. |
I try it in new version of Pyre and it still occurs error. |
So it looks like the issue is that an x86_64 executable is being run in an arm64 architecture, which are incompatible. The best case solution here is that we need to push a new release with an arm64 build, but we unfortunately don't have the infrastructure to do that at the moment. We'll begin to look into doing that so we can start publishing for more platforms. My recommendation at the moment is to try building from source in Docker yourself. Let me know if you have any questions or issues with that, and sorry that we don't have an easier solution for you at the moment. |
when building from source in an linux/arm64 Docker container,I encountered the following error, any help is appreciated.
|
Set the container platform to be amd64: https://stackoverflow.com/questions/65612411/forcing-docker-to-use-linux-amd64-platform-by-default-on-macos And you can set the "Use Rosetta for x86_64/amd64 emulation on Apple Silicon" option under in docker desktop -> settings -> general, which hopefully makes it faster. |
Pyre Bug
Bug description
Running pyre inside a Linux Docker container fails.
Reproduction steps
inside container:
Expected behavior
Once .pyre_configuration has been created the binary fails to execute
Expected type checking to start
Logs
Please include any relevant logs here:
Please run your reproduction steps followed by
pyre rage > pyre_rage.log
, and upload the file here:pyre_rage.log:
Additional context
The text was updated successfully, but these errors were encountered: