From c985de8f80fbf5f7d45b319ee0faa8720067d586 Mon Sep 17 00:00:00 2001 From: soulgalore Date: Sun, 20 Oct 2024 12:14:27 +0200 Subject: [PATCH] docs: update docker container browser versions --- docs/documentation/sitespeed.io/docker/index.md | 6 ++++-- 1 file changed, 4 insertions(+), 2 deletions(-) diff --git a/docs/documentation/sitespeed.io/docker/index.md b/docs/documentation/sitespeed.io/docker/index.md index bbbcbb7b8..07833f863 100644 --- a/docs/documentation/sitespeed.io/docker/index.md +++ b/docs/documentation/sitespeed.io/docker/index.md @@ -68,9 +68,11 @@ Using `-v "$(pwd):/sitespeed.io"` will map the current directory inside Docker a ## Running on Mac M1 ARM -We have ARM container that will be used by default but it will use an older version of Chromium and a newer version of Firefox. The problem is that the Chrome team (Google, 30000+ engineers) do not build Chrome/Chromium on ARM Linux so we rely on *ppa:saiarcot895/chromium-beta* and use the latest version from there. +We have ARM container that will use almost latest version of Chromium (using Microsofts Playwright build) and a newer version of Firefox. -It's probably better to run the AMD containers. If you have a newer version of Docker desktop installed, you can *"Use Rosetta for x86/amd64 emulation"* to run the AMD containers. Go to settings and turn it on (see the screenshot). +If you plan to run Lighthouse in the +1 container, that will not work. Lighthouse uses its own Chrome installation and at the moment Google do not provide a build that work on ARM Linux. + +You can run the AMD containers. If you have a newer version of Docker desktop installed, you can *"Use Rosetta for x86/amd64 emulation"* to run the AMD containers. Go to settings and turn it on (see the screenshot). ![Turn on Rosetta]({{site.baseurl}}/img/rosetta-docker.jpg) {: .img-thumbnail}