docker-node: Pull of "node:8" fails with "no matching manifest for unknown in the manifest list entries" [RESOLVED]
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
About this issue
- Original URL
- State: closed
- Created 6 years ago
- Reactions: 39
- Comments: 22 (1 by maintainers)
Links to this issue
Commits related to this issue
- Hotfix: using node:8.13 images to work around https://github.com/nodejs/docker-node/issues/941 — committed to apify/apify-actor-docker by jancurn 6 years ago
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.
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/
let ALL of the CI pipelines fail.
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.
New tags were pushed a few minutes ago. Now node:11 works for me again.
node:8.13 works, if you’re in a hurry 😄
node:10 come with stretch and no more jessie I use now node:10-jessie image and that works.
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