Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

no matching manifest for linux/amd64 in the manifest list entries #230

Closed
inductor opened this issue Feb 21, 2018 · 33 comments

Comments

@inductor
Copy link

commented Feb 21, 2018

in Dockerfile

FROM nginx:alpine
$ docker-compose build
Building nginx
Step 1/5 : FROM nginx:alpine
alpine: Pulling from library/nginx
ERROR: Service 'nginx' failed to build: no matching manifest for linux/amd64 in the manifest list entries
@uLan08

This comment has been minimized.

Copy link

commented Feb 21, 2018

same here
docker pull nginx:1.13-alpine

1.13-alpine: Pulling from library/nginx
no matching manifest for linux/amd64 in the manifest list entries
@uLan08

This comment has been minimized.

Copy link

commented Feb 21, 2018

I saw in other related issues that this should fix itself after a few mins but it has been an hour since I first encountered the error.
Is it possible to trigger a manual build right now? @tianon

Tagging for future reference
docker-library/official-images#3835

@kb10uy

This comment has been minimized.

Copy link

commented Feb 21, 2018

Same here too.

web:
  image: nginx:mainline-alpine

I got

Pulling web (nginx:mainline-alpine)...
mainline-alpine: Pulling from library/nginx
ERROR: no matching manifest for linux/amd64 in the manifest list entries

Like @uLan08 said, this image seems to be down for long time than other cases.
I hope this recover asap. 🙏

@mattjegan

This comment has been minimized.

Copy link

commented Feb 21, 2018

While the image is down you can possibly get around this issue temporarily using an older image, e.g. nginx:1.12-alpine

@TopFuel

This comment has been minimized.

Copy link

commented Feb 21, 2018

Until this is fixed you can use nginx:stable-alpine, it has an older version of nginx, but it's working fine for me at the moment.

@uLan08

This comment has been minimized.

Copy link

commented Feb 21, 2018

A better approach would probably be to specifically pull an old sha256 digest of nginx:1.13-alpine or whatever tag you're using. This way you won't be pulling an old version of nginx rather just an old build. It is also the recommended workaround in the issue I have linked.
What I did was I viewed the history of the nginx alpine readme, copied and pulled the old digest and tagged it as nginx:1.13-alpine

@rawpixel-vincent

This comment has been minimized.

Copy link

commented Feb 21, 2018

you can also use the previous build directly
FROM nginx:1.13.8-alpine

@kennyrulez

This comment has been minimized.

Copy link

commented Feb 21, 2018

@rawpixel-vincent your snippet did the trick for me. Thanks

@ebernard

This comment has been minimized.

Copy link

commented Feb 21, 2018

@thresheek

This comment has been minimized.

Copy link
Member

commented Feb 21, 2018

And this is why you should never use non-specific versions in your dependent images.

@greuff

This comment has been minimized.

Copy link

commented Feb 21, 2018

I deemed 1.13.9-alpine to be specific enough.

@mustanggb

This comment has been minimized.

Copy link

commented Feb 21, 2018

1.13.9-alpine is specific enough, but it's still the version that hasn't finished building yet, hence why it's not working.

You can see at https://hub.docker.com/r/amd64/nginx/tags/ that 1.13.9-alpine doesn't exist yet.

As @rawpixel-vincent said, use 1.13.8-alpine until the new build is ready.

@bscheshirwork

This comment has been minimized.

Copy link

commented Feb 21, 2018

Pulling nginx (nginx:1.13.9-alpine)...
1.13.9-alpine: Pulling from library/nginx
ERROR: no matching manifest for linux/amd64 in the manifest list entries
d

@bscheshirwork

This comment has been minimized.

Copy link

commented Feb 21, 2018

same situation on mysql 8.0.4
%)
is this illuminati real

gsheasby added a commit to palantir/atlasdb that referenced this issue Feb 21, 2018
gmaretic added a commit to palantir/atlasdb that referenced this issue Feb 21, 2018
* Temporarily use a successfully published version of nginx

Workaround for nginxinc/docker-nginx#230

* [no release notes]
@rolandjitsu

This comment has been minimized.

Copy link

commented Feb 21, 2018

For me only stable-alpine works.

@bscheshirwork

This comment has been minimized.

Copy link

commented Feb 21, 2018

but I wish latest-fresh-hot versions of my favorite tools 😢 I can see 2 hours ago. I can't pull it. It's terrible...

nstapelbroek added a commit to nstapelbroek/docker-static-webserver that referenced this issue Feb 21, 2018
@bscheshirwork

This comment has been minimized.

Copy link

commented Feb 21, 2018

docker pull nginx:1.13.9
1.13.9: Pulling from library/nginx
8176e34d5d92: Pull complete
5b19c1bdd74b: Pull complete
4e9f6296fa34: Pull complete
Digest: sha256:4771d09578c7c6a65299e110b3ee1c0a2592f5ea2618d23e4ffe7a4cab1ce5de
Status: Downloaded newer image for nginx:1.13.9

🏇

@dedsm

This comment has been minimized.

Copy link

commented Feb 21, 2018

not yet nginx:alpine though

@TopFuel

This comment has been minimized.

Copy link

commented Feb 21, 2018

Seems like it's building: https://doi-janky.infosiftr.net/job/multiarch/job/amd64/job/nginx/
Edit: Looks like it's still failing to build properly.

@joekiller

This comment has been minimized.

Copy link

commented Feb 21, 2018

looks like the build is "unstable" so best to lock dependencies for now.

@bndw

This comment has been minimized.

Copy link

commented Feb 21, 2018

As @ebernard alluded to, this appears to be due to Dockerhub's build and release process for official images:

Sometimes, we'll have non-amd64 image build jobs finish before their amd64 counterparts, and due to the way we push the manifest list objects to the library namespace on the Docker Hub, that results in amd64-using folks (our primary target users) getting errors of the form "no supported platform found in manifest list" or "no matching manifest for XXX in the manifest list entries" (see linked issues below for several reports from users of this variety).

Thus, manifest lists under the library are "eventually consistent" -- once all arches complete successfully, the manifest lists get updated to include all the relevant sub-architectures.

docker-library/official-images#3835

A workaround is to use a specific version of a particular tag, e.g. nginx:1.13.8-alpine instead of nginx:alpine

@drpaneas

This comment has been minimized.

Copy link

commented Feb 21, 2018

Same problem here

drpaneas added a commit to drpaneas/os-autoinst-distri-opensuse that referenced this issue Feb 21, 2018
@schmunk42

This comment has been minimized.

Copy link

commented Feb 21, 2018

I have an automated build depending on nginx (rebuilds on updates) - and getting a "failed build" email now every few hours.

I bet this affects a ton of people depending on nginx.

Failed build: https://hub.docker.com/r/schmunk42/nginx-redirect/builds/bpwpbjrbqc7svxkyx8ygxlo/

tianon referenced this issue in docker-library/official-images Feb 21, 2018
- mainline nginx is bumped to 1.13.9
- alpine mainline builds are now using alpine 3.7.
@pzelnip

This comment has been minimized.

Copy link

commented Feb 21, 2018

nginx:alpine now working for me.

@inductor

This comment has been minimized.

Copy link
Author

commented Feb 22, 2018

Works now!
I'll close this issue.

@inductor inductor closed this Feb 22, 2018
StefanBruens added a commit to StefanBruens/os-autoinst-distri-opensuse that referenced this issue Mar 1, 2018
@Primajin

This comment has been minimized.

Copy link

commented Aug 29, 2018

It's happening again 😢
nginx:1.14-alpine works though. Will use this until the issue #262 has been resolved.

@TarCode

This comment has been minimized.

Copy link

commented Aug 29, 2018

It's happening for me too :(

@RancherEdimia

This comment has been minimized.

Copy link

commented Aug 29, 2018

docker pull nginx:alpine
alpine: Pulling from library/nginx
no matching manifest for unknown in the manifest list entries

iainsproat added a commit to cloudfoundry-incubator/kubo-ci that referenced this issue Aug 29, 2018
* docker pull cannot find a manifest for nginx, similar to nginxinc/docker-nginx#230

Signed-off-by: Iain Sproat <isproat@pivotal.io>
@scalp

This comment has been minimized.

Copy link

commented Aug 29, 2018

Same problem here with nginx:1.15-alpine.
Switch to nginx:stable-alpine works for me.

@mageekguy

This comment has been minimized.

Copy link

commented Aug 29, 2018

Same here with nginx:1.15-alpine, used by https://github.com/api-platform/api-platform, ping @dunglas.

@alter

This comment has been minimized.

Copy link

commented Aug 29, 2018

I've switched from nginx:alpine to nginx:stable-alpine too, looks like shit happened

@artem-sabitov

This comment has been minimized.

Copy link

commented Aug 29, 2018

same here
nginx:latest

@pejkosz94

This comment has been minimized.

Copy link

commented Aug 29, 2018

same here.
Change to nginx:stable-alpine and everything works fine.

@nginxinc nginxinc locked as resolved and limited conversation to collaborators Aug 29, 2018
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
You can’t perform that action at this time.