<https://github.com/vesoft-inc/nebula-docker-compo...
# nebula
g
What docker you are using on Mac M1 machines, asking because networking in docker on Mac si functioning a little bit different then on Linux, some functionalities are not supported. You can check in documentation for Docker on Mac.
w
Yes, we are lacking arm console image for now(I may do that later) I(as a m1 user, too) will use the native Darwin_arch64 console binary in my machine though. The cluster itself can be booted in m1(docker desktop/lima etc.) and Raspberry Pi 🙂
@Goran Cvijanovic after docker image being in bi-architecture(since 3.1 as I recall ), no qemu-binfmt(which sufferred from the networking issue you mentioned) will be used in m1 docker-destop/lima to run nebula-docker-compose, and we could play it in arm machine easily now 🙂
w
Its just Docker Desktop straight from docker, no brew or anything like that.
We tried this on two different M1 machines and we got the same failures
w
Yes, plz ignore that for now until https://github.com/vesoft-inc/nebula-console/pull/189 fixed it.
The console there is not fatal, just a helper script to do
ADD HOSTS
. I’ll fix it soon though.