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
Running WebODM on Apple Silicon M1 fails #997
Comments
This problem seems to be related to the cpu architecture of the Apple Silicon M1. The go runtime tries to execute some amd64 instruction, which is not present on the arm architecture. As only the database seems to be affected, my first try was to update this container to a newer version:
This container seems to run, however, I wasn't able to get all the other containers up and running. A
But this leaves me with an error in building the container:
At this point I'm stuck, besides actually not knowing whether my attempts made any sense at all until here. P.S.: I removed some # chars from the quotes as they got interpreted as headings. |
WebODM doesn't have support for M1 as of yet. One would need to rebuild all docker images on M1 (and possibly add some M1 specific patches in the process). It hasn't been done yet. |
That's what I tried to do. I would try to proceed, but I'm a little lost with this error from above:
Do you have an idea what causes this problem, so that I gain insight into it and can proceed trying to get it running on an M1? As I said, I'm a little lost and don't know where to start looking for it. |
I unfortunately don't have an M1, so I'm not sure why that error would appear :( |
I'm sorry that I phrased that mistakeable. I'm not looking for the reason of this error but the part of ODM that could produce it so that I can narrow down the things I need to dig into to possibly find a solution. |
Looks that it might be an error with the PROJ library; check that the PROJ database is correctly installed perhaps. |
node js also support M1 after version 15. |
Thank you for the hints. I already switched to Py3.9, but the Node.js change I have to keep in mind. Actually, I changed the plan a little bit. Right now I'm trying to get ODM running natively on the M1. Once this is done, I want to adopt those changes to/learn from those changes for WebODM. The problem I'm facing right now is to build OpenSfm, which is still failing in the configure step. I think this is due to the glibc, but this is just a rough guess. Still digging... |
Wow, I'm looking forward to it. 👍🏻
2021년 6월 17일 (목) 오후 7:40, pvitt ***@***.***>님이 작성:
… node js also support M1 after version 15.
that's why I think change https://deb.nodesource.com/setup_12.x to
https://deb.nodesource.com/setup_16.x
and python also arm64 support after 3.9.1
Thank you for the hints. I already switched to Py3.9, but the Node.js
change I have to keep in mind.
Actually, I changed the plan a little bit. Right now I'm trying to get ODM
running natively on the M1. Once this is done, I want to adopt those
changes to/learn from those changes for WebODM. The problem I'm facing
right now is to build OpenSfm, which is still failing in the configure
step. I think this is due to the glibc, but this is just a rough guess.
Still digging...
—
You are receiving this because you commented.
Reply to this email directly, view it on GitHub
<#997 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/ABPGQ6ETCMIGKSCJ5GLPOWDTTHGKVANCNFSM46OIYT2Q>
.
|
A fund is now open toward this effort. https://fund.webodm.org/#/fund/6 |
Looks like the effort is funded. Hooray! Any update on getting this fixed? |
The effort was completed, so WebODM should work on M1 now (forgot to close this issue)! Just make sure to update via |
It works! Thank you!! |
What's your browser and operating system? (Copy/paste the output of https://www.whatismybrowser.com/)
Firefox 89 on macOS (Catalina)
What is the problem?
When running WebODM, the db container keeps restarting. It keeps throwing errors like this:
What should be the expected behavior?
The db container should run.
How can we reproduce this? (What steps did you do to trigger the problem? What parameters are you using for processing? Please include multiple screenshots of the problem! If possible please include a copy of your dataset uploaded on Google Drive or Dropbox. Be detailed)
I basically installed WebODM as described in the manual.
The text was updated successfully, but these errors were encountered: