It is possible to build Odoo Docker image for darwin/arm64 Macbook with M1 CPU?

[vasi26ro]

Hello,
I use doodba, and it is a really impressive tool. Recently I have changed my laptop with a Macbook with M1 CPU.
I have tried to set up a development environment on this laptop, but I cannot run the odoo image since there is a limitation regading inotify and qemu.

However, attempts to run Intel-based containers on Apple silicon machines under emulation can crash as qemu sometimes fails to run the container. In addition, filesystem change notification APIs (inotify) do not work under qemu emulation. Even when the containers do run correctly under emulation, they will be slower and use more memory than the native equivalent.

Source: https://docs.docker.com/desktop/mac/apple-silicon/

How can I build the image for M1?

[piqoni]

In which image do you get the error?

[vasi26ro]

In the odoo image

development-env-odoo-1                        |     self._i = Inotify(block_duration_s=block_duration_s)
development-env-odoo-1                        |   File "/usr/local/lib/python3.8/site-packages/inotify/adapters.py", line 57, in __init__
development-env-odoo-1                        |     self.__inotify_fd = inotify.calls.inotify_init()
development-env-odoo-1                        |   File "/usr/local/lib/python3.8/site-packages/inotify/calls.py", line 34, in _check_nonnegative
development-env-odoo-1                        |     raise InotifyError("Call failed (should not be -1): (%d)" % 
development-env-odoo-1                        | inotify.calls.InotifyError: Call failed (should not be -1): (-1) ERRNO=(0)
development-env-odoo-1                        | Exception ignored in: <function Inotify.__del__ at 0x4007c65940>
development-env-odoo-1                        | Traceback (most recent call last):
development-env-odoo-1                        |   File "/usr/local/lib/python3.8/site-packages/inotify/adapters.py", line 79, in __del__
development-env-odoo-1                        |     os.close(self.__inotify_fd)
development-env-odoo-1                        | AttributeError: 'Inotify' object has no attribute '_Inotify__inotify_fd'

[edipiqoni]

I remember I have circumvented this one by not using reload/inotify option. (maybe its called "dev mode", not sure now)

Basically it fails in this line in server.py:

For the root cause, here's an issue (and related issues) which could be a starting point if you want to investigate further: docker/for-mac#6174

[jigypeper]

Hi, did you ever get a fix for running the container on apple silicon? I am getting :

[+] Running 2/7
✘ odoo_proxy Error 5.1s
✘ proxy_www_google_com Error 5.1s
⠙ proxy_cdnjs_cloudflare_com Pulling 5.1s
⠙ proxy_fonts_googleapis_com Pulling 5.1s
⠙ proxy_fonts_gstatic_com Pulling 5.1s
⠙ proxy_www_googleapis_com Pulling 5.1s
⠙ proxy_www_gravatar_com Pulling 5.1s
no matching manifest for linux/arm64/v8 in the manifest list entries

[vasi26ro]

Hi, did you ever get a fix for running the container on apple silicon? I am getting :

[+] Running 2/7

✘ odoo_proxy Error 5.1s

✘ proxy_www_google_com Error 5.1s

⠙ proxy_cdnjs_cloudflare_com Pulling 5.1s

⠙ proxy_fonts_googleapis_com Pulling 5.1s

⠙ proxy_fonts_gstatic_com Pulling 5.1s

⠙ proxy_www_googleapis_com Pulling 5.1s

⠙ proxy_www_gravatar_com Pulling 5.1s

no matching manifest for linux/arm64/v8 in the manifest list entries

This error is because there is no image build for linux/arm64/v8 platform.

You can build a image for this platform or use the platform: linux/amd64 keyword in docker-compose. The latter option on my laptop was slow.

[jigypeper]

as well as rebuilding for arm?

[theangryangel]

@jigypeper reach out to me on Monday please and I will try and help explain the problem(s) you're seeing, and why we've not put any effort into this yet.

[jigypeper]

I will do!!

[bosd]

There is a pr in: Tecnativa/docker-whitelist#15 :)

[jigypeper]

Switching to orbstack fixed the issues I was having.
Could carry on development as before.