Docker Compose + Selenoid + Chrome на Apple M1

dizzypot · 18.Ноябрь.2022 06:03:37

Перехожу на Apple M1 с Windows.
Подскажите, есть у кого опыт запуст контейнеров с Chrome на arm64/m1?

У меня не получается успешно запустить.

asolntsev · 18.Ноябрь.2022 09:41:51

У меня тоже не получается.
Кажется, официально Selenoid пока не поддерживает M1.

Зато нашёл такую инструкцию: Selenoid Mac M1 · GitHub

dizzypot · 13.Декабрь.2022 15:12:45

Chrome arm64 image:
https://hub.docker.com/r/sskorol/selenoid_chromium_vnc/tags

github.com/aerokube/images

Initial Chromium image support for arm64

aerokube:master ← sskorol:add-arm64-chromium-support

opened 05:41PM - 03 May 22 UTC

sskorol

+325 -4

Initial implementation of a Chromium image for arm64 which is required to run Se…lenoid on M1. See [build-chromium.sh](https://github.com/aerokube/images/blob/ef468d461f827705d1445a366192106fd6b56ace/build-chromium.sh) (TBR) for details or just [pull sskorol/selenoid_chromium_vnc:100.0](https://hub.docker.com/r/sskorol/selenoid_chromium_vnc/tags) for testing. Note that your `browsers.json` should label this image as chrome: ```json "chrome": { "default": "100.0", "versions": { "100.0": { "image": "sskorol/selenoid_chromium_vnc:100.0", "port": "4444" } } } ``` Your Selenium tests should pass a `browserName = chrome` capability as `chromium` isn't explicitly supported for filtering. The base image was downgraded to ubuntu:18.04 as Focal doesn't have fresh updates for Chromium. Also, note that `libgtk-3-0` package is required for the Chromium image. Otherwise, a browser just crashes in runtime with a 500 error from Selenoid. Fixes https://github.com/aerokube/images/issues/449 @vania-pooh feel free to review and revise if required. I haven't tested all the potential scenarios (with /local build and dev tools).

Забыл отписать: мне удалось всё завести
использовал данный образ

Уже месяц стабильно всё работает