Open-Assistant icon indicating copy to clipboard operation
Open-Assistant copied to clipboard

Breaks on Mac M1

Open sfabriece opened this issue 2 years ago • 16 comments

I'm getting the following error when spinning up on a Mac with an M1:

Error response from daemon: platform linux/arm64/v8 not supported

image

sfabriece avatar Jan 09 '23 12:01 sfabriece

What version of docker do you have?

I have a Mac M1 and I am not seeing any problems right now (tho i have in the past).

fozziethebeat avatar Jan 09 '23 12:01 fozziethebeat

image

sfabriece avatar Jan 09 '23 12:01 sfabriece

Any Ideas @fozziethebeat :)

sfabriece avatar Jan 10 '23 08:01 sfabriece

Not yet. I'm assuming you tried to bring everything up by running docker compose up --build correct?

fozziethebeat avatar Jan 10 '23 08:01 fozziethebeat

I did @fozziethebeat. Do you have the same version? image

sfabriece avatar Jan 10 '23 08:01 sfabriece

So, I just double checked and it turns out I have a Mac M2, not a M1 (I seem to have forgotten what I recently purchased). That could be the key problem.

We have the same version of docker. The one setting difference is that i use gRPC FUSE instead of VirtioFS. I'm not sure that would affect this however.

What version of MacOS do you have? I have 13.1 (22C65)

fozziethebeat avatar Jan 10 '23 08:01 fozziethebeat

I have the same MacOS version as you @fozziethebeat. I there any specific reason you are using gRPC FUSE instead of the others?

sfabriece avatar Jan 10 '23 08:01 sfabriece

This was the default setting for my Docker. I actually haven't inspecting these settings so i'm not quite sure how it got set.

fozziethebeat avatar Jan 10 '23 09:01 fozziethebeat

the sleep images can easily be replaced, but it's super strange that the backend image is an amd, because if you're doing --build, then that should be built locally. is this due to the base image?

yk avatar Jan 10 '23 09:01 yk

I also have an M1 macbook. By default my docker was also using gRPC FUSE which indeed doesn't give error or warnings. On the other hand I tried to reproduce what @sfabriece said and I get the same warning though they are still not blocking, (the not supported container just run under emulation). In general since gRPC FUSE seems to be the default version I do not think this is too alarming, since with that default setting it works like a charm. If I can help any other way I'd be glad to tray to help though.

Jac-Zac avatar Jan 10 '23 22:01 Jac-Zac

@Jac-Zac I didn't understand your previous comment. Did you manage to reproduce my issue? 😄

sfabriece avatar Jan 11 '23 08:01 sfabriece

Yeah sorry. But using gRPC FUSE it works for me

Jac-Zac avatar Jan 11 '23 08:01 Jac-Zac

And using VirtioFS I get the same warnings

Jac-Zac avatar Jan 11 '23 08:01 Jac-Zac

Btw, I'm on macOS Ventura 13.1 (22C65)

Jac-Zac avatar Jan 11 '23 08:01 Jac-Zac

Good to know that someone else get the same errors. @Jac-Zac

sfabriece avatar Jan 11 '23 09:01 sfabriece

There's a regression in Docker Desktop somewhere between 4.15.0 and 4.16.2. The former works fine.

Edit: Lol, when posting, I thought I was in the Docker org— probably is useful for y'all too though!

nicosuave avatar Jan 31 '23 22:01 nicosuave

Looks like this has a solution. Closing it but if anyone still has the problem feel free to reopen

olliestanley avatar Feb 05 '23 11:02 olliestanley

Disabling experimental containerd support in Docker Desktop solves this problem (broadly, beyond this repo) for me

nicosuave avatar Feb 05 '23 17:02 nicosuave

@nicosuave: saved my day 🙇‍♂️

jagui avatar Feb 08 '23 15:02 jagui