-
Notifications
You must be signed in to change notification settings - Fork 17
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] Iris-Compatibility issue with M1 Mac and docker container #376
Comments
This is a problem with the node itself as you already mentioned here aeternity/aeternity#3632. |
should be fixed if aeternity/aeternity#3846 is solved and a new release is published afterwards |
actually we already have a working image. @omar-saadoun @thepiwo is this m1 image somewhere public and can be explicitly manually set by users? |
As far as I know there hasn't been a production read image been published yet |
didn't you publish this workaround image somewhere? just in case somebody really wants to play around with it (knowing it's not the prod-ready image) |
I'm playing around with it |
Its finally fixed using aeproject 4.6.0 https://github.com/aeternity/aeproject/releases/tag/v4.6.0 |
Describe the bug
When starting the environment as usual with aeproject env it get stopped when starting the node and funding wallets.
Checking on logs for the node I get this:
Exec: /home/aeternity/node/erts-10.7.2.3/bin/erlexec -boot /home/aeternity/node/releases/6.0.0-rc3/aeternity -mode embedded -boot_var SYSTEM_LIB_DIR /home/aeternity/node/lib -config /home/aeternity/node/releases/6.0.0-rc3/sys.config -args_file /home/aeternity/node/releases/6.0.0-rc3/vm.args -- console -noinput -aehttp enable_debug_endpoints true
Root: /home/aeternity/node
/home/aeternity/node
sigaltstack: Invalid argument
sigaltstack: Invalid argument
qemu: uncaught target signal 6 (Aborted) - core dumped
Doing some research it seems that there is some issue between OTP version, docker and M1 Mac processors.
docker/for-mac#5148
Aeproject information (please complete the following information):
The text was updated successfully, but these errors were encountered: