search

containous / traefik-library-image

ARCHIVED
https://github.com/traefik/traefik-library-image
Apache License 2.0
218 stars 60 forks source link

Pulling traefik:v1.4.2 fails with not matching manifest for linux/amd64 #20

Closed haster closed 6 years ago

haster commented 6 years ago

I can't pull the scratch/amd64 images (at least 1.4) because there is no matching manifest for linux/amd64? The alpine image seems to work just fine.

haster@schootbak3:~
$ docker run -d -p 8080:8080 -p 80:80 -v $PWD/traefik.toml:/etc/traefik/traefik.toml traefik
Unable to find image 'traefik:latest' locally
latest: Pulling from library/traefik
docker: no matching manifest for linux/amd64 in the manifest list entries.
See 'docker run --help'.

haster@schootbak3:~
$ docker run -d -p 8080:8080 -p 80:80 -v $PWD/traefik.toml:/etc/traefik/traefik.toml traefik:v1.4.2
Unable to find image 'traefik:v1.4.2' locally
v1.4.2: Pulling from library/traefik
docker: no matching manifest for linux/amd64 in the manifest list entries.
See 'docker run --help'.

haster@schootbak3:~
$ docker run -d -p 8080:8080 -p 80:80 -v $PWD/traefik.toml:/etc/traefik/traefik.toml traefik:v1.4
Unable to find image 'traefik:v1.4' locally
v1.4: Pulling from library/traefik
docker: no matching manifest for linux/amd64 in the manifest list entries.
See 'docker run --help'.

haster@schootbak3:~
$ docker run -d -p 8080:8080 -p 80:80 -v $PWD/traefik.toml:/etc/traefik/traefik.toml traefik:v1.4-alpine
Unable to find image 'traefik:v1.4-alpine' locally
v1.4-alpine: Pulling from library/traefik
b56ae66c2937: Pull complete 
622747cc946a: Pull complete 
38ac1701549a: Pull complete 
625397284ae3: Pull complete 
Digest: sha256:6557adf3f4e3ec101f59f1d419f69ab22bf56b02bc6c14750461bc8818061be0
Status: Downloaded newer image for traefik:v1.4-alpine
07ca2b2a83ca03ebef4c5ee108d464b17258a23e2ac5c2069f081c33ce554ea9
mmatur commented 6 years ago

Hi, There is an issue with last docker images build: https://github.com/docker-library/official-images/pull/3668#issuecomment-341636393

Gilead commented 6 years ago

@ldez So what is the current situation? You closed all issues as if everything was fine but there is no new release so the problem persists. Where do we look to find if the problem has been solved?

ldez commented 6 years ago

@Gilead The problem is at Docker, we can not do anything directly. We have to wait for San Francisco to wake up.

Gilead commented 6 years ago

OK, thanks.