New user here, and I’m trying to get the basic Dgraph tour running on my mac mini M1. Docker on the M1 is still not an official release, I am using this [Apple Silicon Tech Preview | Docker Documentation]
Used the standalone docker image - Dgraph crashes on the first mutation instruction.
Built Dgraph from source - Dgraph alpha seems to fail to initialize, I keep getting an IO412 and EO412 errors in the console logs. I am using instructions from this page https://dgraph.io/docs/deploy/single-host-setup/
I don’t know of any other options to try out Dgraph - please let me know what’s the suggested route.
I am investigating in building a new kind of supply chain optimization platform using Dgraph, any help would be appreciated, thanks!
Hi, while initially there was work and excitement going into making Dgraph work with M1 (and AWS Graviton), it turned out to require more manpower than expected. So for now we have temporarily Dropping support for Windows and Mac
Having said that, if you could give me some time, I could probably make it work for you.
I did try with Go 1.16. It seems there is a problem with initializing alpha.
W0419 14:39:06.168760 4038 pool.go:267] Connection lost with localhost:5080. Error: rpc error: code = Unavailable desc = connection error: desc = "transport: Error while dialing dial tcp [::1]:5080: connect: connection refused"
E0419 14:39:07.066558 4038 groups.go:1177] Error during SubscribeForUpdates for prefix "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x15dgraph.graphql.schema\x00": Unable to find any servers for group: 1. closer err: <nil>
E0419 14:39:08.067435 4038 groups.go:1177] Error during SubscribeForUpdates for prefix "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x15dgraph.graphql.schema\x00": Unable to find any servers for group: 1. closer err: <nil>
E0419 14:39:09.067664 4038 groups.go:1177] Error during SubscribeForUpdates for prefix "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x15dgraph.graphql.schema\x00": Unable to find any servers for group: 1. closer err: <nil>
E0419 14:39:10.068887 4038 groups.go:1177] Error during SubscribeForUpdates for prefix "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x15dgraph.graphql.schema\x00": Unable to find any servers for group: 1. closer err: <nil>
I0419 14:39:11.066028 4038 admin.go:824] Error reading GraphQL schema: Please retry again, server is not ready to accept requests.
E0419 14:39:11.069619 4038 groups.go:1177] Error during SubscribeForUpdates for prefix "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x15dgraph.graphql.schema\x00": Unable to find any servers for group: 1. closer err: <nil>
E0419 14:39:12.070544 4038 groups.go:1177] Error during SubscribeForUpdates for prefix "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x15dgraph.graphql.schema\x00": Unable to find any servers for group: 1. closer err: <nil>
E0419 14:39:13.072708 4038 groups.go:1177] Error during SubscribeForUpdates for prefix "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x15dgraph.graphql.schema\x00": Unable to find any servers for group: 1. closer err: <nil>
E0419 14:39:14.074814 4038 groups.go:1177] Error during SubscribeForUpdates for prefix "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x15dgraph.graphql.schema\x00": Unable to find any servers for group: 1. closer err: <nil>
E0419 14:39:15.077216 4038 groups.go:1177] Error during SubscribeForUpdates for prefix "\x00\x00\x00\x00\x00\x00\x00\x00\x00\x00\x15dgraph.graphql.schema\x00": Unable to find any servers for group: 1. closer err: <nil>
I’m letting you know that it is April 2022 and it appears that the Docker standalone image will not run on Mac M1. You can’t even buy Mac Intel anymore. Haven’t been able to for several months. Is an M1 docker image coming soon?
Dgraph Labs is still functional and there would definitely be continuation of service. Here’s the official announcement pertaining to the same.
I agree, we should have an ARM64 build available today. We’d encountered issues in the past during compilation when using a tool called xgo. I reckon, xgo was chosen due to the fact that it simplifies cross-compilation of Go code that uses CGO, which otherwise is non-trivial as you need access to platform-specific libs and headers.
IMO the best path forward is to address issues seen with xgo last, as that would also help for adding support for other platforms and architectures. But we are now aware of the situation and open to exploring all other possibilities as well, just in case.