It seems like nginx:latest is now broken

[franklouwers]

When using nginx:latest to start a service on a Docker EE with Swarm worker nodes, the containers refuse to start. When using nginx:stable, everything works fine.

I believe this still worked yesterday, so it must be a recent change.

[benlamptey]

yeah, I'm having the same issue

Pulling nginx (nginx:latest)... latest: Pulling from library/nginx ERROR: no matching manifest for unknown in the manifest list entries

[dylanrhysscott]

Same for me :(

[assafnielsen]

I can confirm we are having the same issue with nginx latest image

[bghellofresh]

$ docker run -it --rm nginx:latest sh
Unable to find image 'nginx:latest' locally
latest: Pulling from library/nginx
docker: no matching manifest for linux/amd64 in the manifest list entries.
See 'docker run --help'.

can confirm stable tag works.

[mystetskyivlad]

Same issue for us

[MarcioMateus]

I have the same problem with nginx:alpine

alpine: Pulling from library/nginx docker: no matching manifest for unknown in the manifest list entries. See 'docker run --help'.

[avielb]

I am able to pull:

 docker pull nginx:1.14

1.15 isn't working

[julio641742]

It is a problem with docker infrastructure. See #240 for more details

[apollotonkosmo]

same here with nginx:latest . nginx:stable works though.

[kjelle]

Same here

[tudor2004]

same here with nginx:alpine

[Primajin]

go for nginx:1.14-alpine until it's fixed.

#230

[ivan-kolmychek]

It may be related to docker-library/official-images#3835

[chrootlogin]

Same issue here

[nbukhter]

Hi, I have the same issue with nginx:alpine

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

Is there any ETA to resolve this issue?

[thresheek]

As @julio641742 mentioned earlier, this is a problem with Docker infrastructure and not an nginx image itself. Please don't add more "same issue" -- that does not help.

I've notified docker team about the issue, unfortunately there is no ETA yet. Thanks for understanding.

[KrzysztofKarol]

All images 1.15.3, mainline, 1, 1.15, latest (mainline/stretch/Dockerfile) points to 1.15.3 which is currently unavailable due to Docker infrastructure problem.
I "downgraded" nginx:1.15.3-alpine to nginx:1.15.2-alpine and it's working for me so it should work for "normal" (nginx:1.15.2) version

[thresheek]

The issue is now fixed, AFAICT.

thresh@coal ~ $ docker pull nginx:latest
latest: Pulling from library/nginx
be8881be8156: Already exists 
65206e5c5e2d: Pull complete 
8e029c3e2376: Pull complete 
Digest: sha256:291e15f504cdc40aeedcd29b59f0079c794e18f22cd8a6a6d66d646b36f1d51b
Status: Downloaded newer image for nginx:latest
thresh@coal ~ $ docker run -ti --rm nginx:latest nginx -V
nginx version: nginx/1.15.3