-
Notifications
You must be signed in to change notification settings - Fork 190
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
Issue Running von-network On M1 Chip Mac Machine #182
Comments
Could you provide the logs? Run the following to first clear the logs so you have a clean run and then start
|
Here are the logs attached |
Looks like it's an architecture issue. There is a hint to this in the logs:
If you do a google search on The base image for The source for the base image is here PSPC-SPAC-buyandsell/von-image; the |
There are also indications this is a bug in qemu (a component used for running Intel (amd64) containers on M1 (arm64) chips). Upgrading that component may help too. |
Thanks @WadeBarnes I will try those options. Thanks again for your help. |
Running into the same problem. @Tarunshrma have you already tried to build a von image image for |
@TimoGlastra I ran into the same problem, but I finally managed to run the network on Apple Silicon by tweaking and rebuilding the underlying PSPC-SPAC-buyandsell/von-image as a arm64 variant. You can review the changes in my fork of von-image. Although I was not (yet) able to compile the postgres plugin, I'm able to run the von-network by replacing the base image in von-network's Dockerfile with my custom von-image. Because the plugin does not compile, I just made a quick test by pointing the browser to the web server at localhost:9000 You can find instructions to build the von-image yourself and the changes necessary to the von-network's Dockerfile in the README of the fork or just let the Dockerfile pull my image from hub.docker.io (starting FROM snel/von-image:node-1.12-4-arm64) |
@nebucaz, Thanks for the update and the work on |
@WadeBarnes I will be happy to do that, but I fear, I'll not make it in a reasonable time, because, I do not really understand der problem: It is located in the file Compiling on Ubuntu Linux aarch64 fails in an unsafe block:
When replaced with |
@nebucaz are you just creating the von-image for von network/indy node? In this scenario I don't think the postgres plug-in is required. |
@ianco, the postgres plugin is part of the base image used for |
@nebucaz, The data types in the |
@WadeBarnes correct but I don't think it's actually required. It's used by Indy SDK for wallet storage, however nodes (I believe) don't have wallets or use postgres, and the ledger browser uses a wallet but I believe using default storage (sqlite) |
It's used in |
Ah ok got it thanks |
@WadeBarnes Thanks for the hint to |
Hi, @nebucaz. Suffering same pain as you did but not able to resolve it since I don't have tech background. I'm following course Edx LFS173x with an M1 mac. when I try to run LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber --events --no-auto --bg I got stuck with the WARNING: The requested image's platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested. I have been reading all the issues and see you have the answer. The problem is that I believe run_demo faber is bringing von-image version different from the one you have forked and don't know how to continue. I suppose I have to make some modifications in my code in order to call the new arm64 version but no clue how to do it. Thanks anyone for your general efforts and your indications with command line example. |
Hi @vectoria-org I'm sorry, but I Have been assigned to another project in January 2022 and therefore have not been involved nor have managed to assign any spare time on this issue. I've built my own version of the underlying von-image and referenced this image in Dockerfile of von-network:
You can then build your own 'von-network-base' docker image based on snel/von-image.
You can then start the von-network using
And watch the logs with
As you can see, I also have the warning, but I'm not able to provide more support without considerable effort.
And the Web server is accessible on Did you try to run the demo in the docker-environment (http://play-with-von.vonx.io/) rather than local? |
Many thanks for your support @nebucaz. I'm running this command LEDGER_URL=http://dev.greenlight.bcovrin.vonx.io ./run_demo faber --events --no-auto --bg when linux/arm64 warning appears. Yesterday suddenly worked, after executing commands pyenv and pipenv but not sure yet how that happened. |
Hello back @nebucaz. I'm copy-pasting here the solution that worked in my mac and hopefully it will for others. It is not possible for me to explain it better so let me post the code here and hopefully there will be other contributor with tech background that can summarize better. @MacBook-Air-de-Julio-3 ~ % python3 -m venv ./venv You have 13 outdated formulae installed. ==> Downloading https://ghcr.io/v2/homebrew/core/autoconf/manifests/2.71 ==> Pouring folly--2022.10.17.00.arm64_monterey.bottle.tar.gz ==> Pouring edencommon--2022.10.17.00.arm64_monterey.bottle.tar.gz ==> Pouring fizz--2022.10.17.00.arm64_monterey.bottle.tar.gz ==> Pouring wangle--2022.10.17.00.arm64_monterey.bottle.tar.gz ==> Pouring fbthrift--2022.10.17.00.arm64_monterey.bottle.tar.gz ==> Pouring fb303--2022.10.17.00.arm64_monterey.bottle.tar.gz ==> Pouring [email protected]_monterey.bottle.1.tar.gz ==> Pouring watchman--2022.10.17.00.arm64_monterey.bottle.tar.gz ==> Pouring node--18.11.0.arm64_monterey.bottle.tar.gz ==> Pouring unbound--1.17.0.arm64_monterey.bottle.tar.gz Some useful pyenv commands are: See Options: Usage Examples: Remove project virtualenv (inferred from current directory): Install all dependencies for a project (including dev): Create a lockfile containing pre-releases: Show a graph of your installed dependencies: Check your installed dependencies for security vulnerabilities: Install a local setup.py into your virtual environment/Pipfile: Use a lower-level pip command: Commands: ✔ Successfully created virtual environment! We changed requirements.txt to: But a few days later Alice Docker did not work and we made another change, to: It works now smoothly so hopefully someone who understands what we did can explain it better so others to come can solve the issue and follow the course LinuxFoundationX LFS173x with an M1 Mac. Regards. |
Hi,
I am following the provided documentation to run von-network locally on my M1 based machine. "./Manage start" command stats the 4 containers for node and 1 for web server. When I try to open http://localhost:9000 web server is not accessible and subsequently other node containers are also exit. I am getting below error:
qemu: uncaught target signal (Aborted) - core dumped.
The text was updated successfully, but these errors were encountered: