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

[trivikr]

trafficstars

The following error is thrown when attempting to run docker pull on M1 MBP

$> docker pull nodejs/devcontainer:nightly
nightly: Pulling from nodejs/devcontainer
...
no matching manifest for linux/arm64/v8 in the manifest list entries

[trivikr]

This likely happens since image is not available for ARM64 architecture. A workaround is to add --platform linux/amd64 to pull an Intel image under emulation.

[bharath063]

https://github.com/nodejs/node/pull/54757 This PR might help with this

@trivikr

[bnb]

I can try to fix this soon! Please feel free to create a PR to fix if someone else finds a soluton.

[sdavids]

Is this still being worked on?

Alternatively, you might want to retire this repo and direct people to mcr.microsoft.com/devcontainers/javascript-node:1-22-bookworm for example.

[joyeecheung]

I tried to fix it in https://github.com/nodejs/devcontainer/pull/13 but it seems building arm64 in emulation made the build take a very long time and exceeds the 6h limit. Now I can try to extend the build time limit to 24h (that seems to be maximum) and see if that works. But I wonder if there's a way to split them into different actions so that we can build arm64 images on arm64 runners without emulation..

[joyeecheung]

Alternatively, you might want to retire this repo and direct people to mcr.microsoft.com/devcontainers/javascript-node:1-22-bookworm for example.

That is different from what this repo does, this repo maps to local clones of Node.js for developing Node.js per-se, not for developing an app that runs on Node.js - at least, not for stable Node.js, at most for testing it against nightly Node.js

[joyeecheung]

I think this should make it work: https://github.com/nodejs/devcontainer/pull/14

[joyeecheung]

This should be fixed by https://github.com/nodejs/devcontainer/pull/14 now.