Wanted the server and web UI without installing anything, so I went for the image:
docker run --rm -p 8080:8080 -v sdods-data:/data ghcr.io/yarlisaisolutions/sdods-serverno matching manifest for linux/arm64/v8 in the manifest list entriesI thought Docker Desktop emulated whatever was missing on Apple silicon. It seems not, or I have misunderstood something.
Accepted answer
You have not misunderstood the machine, only Docker. Docker does not fall back to emulation for a missing architecture — it refuses the pull. Emulation only happens once you ask for a platform it can emulate, which is what the flag does:
docker run --rm --platform linux/amd64 -p 8080:8080 -v sdods-data:/data ghcr.io/yarlisaisolutions/sdods-serverThe published image is linux/amd64 only today, so on Apple silicon it goes through Rosetta. It works and it is slower — mostly on startup rather than during a run.
On an Intel machine, or once an arm64 image is published, no flag is needed.
The reason it is amd64 only, since it comes up every time: building arm64 in CI was tried and abandoned. Under emulation on an amd64 runner the arm64 stage did not finish inside the job limit, because the dependency install, the native module builds and the web bundle all run emulated. Fixing it properly needs a native arm64 runner or splitting the build so the architecture-independent part is not emulated.
The install page reads the architectures out of the actual manifest rather than a claim in a config file, which is why it says amd64 rather than quietly promising both.
If the emulated startup bothers you, the CLI is native on Apple silicon and installs in under a minute:
curl -fsSL https://sdods.com/install.sh | shThe image is the better choice when you want the server and web UI without installing anything on the host. For running suites locally the CLI is the faster path on that hardware.
Have a different question? Ask it.