-
Notifications
You must be signed in to change notification settings - Fork 2k
Description
Environment
Platform: Raspbian 12 bookworm
- Docker Version: Docker version 28.5.1, build e180ab8
- Node.js Version: > 22
- Image Tag:
Expected Behavior
I expected, that there are docker images for node > 22 which I can pull using docker pull.
Current Behavior
I'm using docker pull node:24 but I get the error
24: Pulling from library/node
no matching manifest for linux/arm/v8 in the manifest list entries
Possible Solution
I assume someone need to create those images.
I also tried docker pull arm64v8/node:25-alpine with the same error.
Steps to Reproduce
Try docker pull node:24 on a raspberry pi 5.
Additional Information
In general I would be interested if a new node version requires a newly created issue here in github or should new versions be it minor or major be released automatically?
I'm just interested in how the node workflow is in this case if a new fixes or versions are created,
because there are other closed issues also with the same no matching manifest errors which, then, seemed to have been created kind of manually.
So, is it intentional that a new node version for raspberry/arm requires a new github issue?
Many thanks for your time and maintaining node.