Pull of "node:8" fails with "no matching manifest for unknown in the manifest list entries" [RESOLVED]

[jancurn]

Our Docker builds and deploys based on the node:8 image started to fail today.

$ docker pull node:8
8: Pulling from library/node
no matching manifest for unknown in the manifest list entries

[njgage]

Yep, I just had the same issue with node: 8

[aogilvie]

You can pull FROM node:8.13

but yeah, the new builds are all broke.
New builds went out 20mins ago (as of writing) but they are all defunct.

https://hub.docker.com/r/library/node/tags/

[wlodi83]

I have the same issue with node:carbon

Step 1/47 : FROM node:carbon as intermediate
carbon: Pulling from library/node
no matching manifest for unknown in the manifest list entries

[petri8]

Same with carbon here

[erickwilder]

I have the same with node:11.3.0

[ravidhu]

same here with node: 8

[LaurentGoderre]

@tianon do you have any idea what this means?

[grnadav]

same for node:10-jessie

[aogilvie]

@LaurentGoderre Probably missing architectures. unknown should be a listed arch.

Hinted to in this post docker-library/official-images#3835 by @tianon

[aogilvie]

As more people arrive here (I expect there will be a lot of traffic), just to note; you CAN still get builds if you use the tags published yesterday (until things are fixed). See my link above.

[yue-wen]

same for node:carbon-slim

[fiws]

let ALL of the CI pipelines fail.

[petri8]

node:8.13 works, if you're in a hurry :D

[fabiante]

Anyone found a node:10 image that works?

[luontola]

New tags were pushed a few minutes ago. Now node:11 works for me again.

[fabiante]

New tags were pushed a few minutes ago. Now node:11 works for me again.

Same for node:10-slim

[Oxalide-Team-2]

node:10 come with stretch and no more jessie
I use now node:10-jessie image and that works.

[ravidhu]

node:8 work again !

[mansetaashok]

I have a same error : "Pulling from library/node
no matching manifest for unknown in the manifest list entries"

I am building Azure Pipeline for my Nodejs application using Host VS2017 agent. It is working fine in my local system, However while doing DevOps pipeline setup the error encountered.

I have also tried different versions of node as base image in my docker file. But no luck.

Can anyone please help for the same.

[kakarotto67]

@mansetaashok , I have the same issue, tried different versions but didn't work. Were you able to fix this somehow?

[kakarotto67]

Ok, I used custom node for windows from here and it worked.

Changed
ARG NODE_IMAGE=node:12.2
to
ARG NODE_IMAGE=stefanscherer/node-windows:latest

since I'm using windows-based containers.

[mansetaashok]

@kakarotto67, It did not work for me in Hosted VS2017. I have changed to the Linux Agent Hosted Ubuntu and it worked. Thank you for sharing the custom node image for Windows.