Giters

c0b / docker-elixir

Official Docker image for Elixir :whale: :turtle: :rocket:

Home Page:http://elixir-lang.org/

Geek Repo:Geek Repo

Github PK Tool:Github PK Tool

No matching manifest for linux/amd64 in the manifest list entries

dhoeric opened this issue · comments

commented

Got the above error when running docker pull elixir:1.6.4-alpine in my linux machine.

Detail message

$ docker pull elixir:1.6.4-alpine
1.6.4-alpine: Pulling from library/elixir
no matching manifest for linux/amd64 in the manifest list entries

And looks like the image in linux/amd64 architecture is missing.

$ docker manifest inspect elixir:1.6.4-alpine
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
   "manifests": [
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 1158,
         "digest": "sha256:3c4b0b23e762491acc44dcba44c2e1f7a04942523e54204f97ee94a386159e8f",
         "platform": {
            "architecture": "ppc64le",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 1158,
         "digest": "sha256:bc1f54d2015114bf177520d2c0a7e85e40b81741f051d163d3912a7391b99733",
         "platform": {
            "architecture": "s390x",
            "os": "linux"
         }
      }
   ]
}

Is there any CI to build in linux/amd64 architecture as well?

commented

Having the same error, we are using elixir:1.6 image on circle, not alpine.

elixir:1.6.3 seems to work

commented

Seems to be back for me

commented

Yeah, it's work now. Would be nice to know the reason! :)

$ docker manifest inspect elixir:1.6.4-alpine
{
   "schemaVersion": 2,
   "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
   "manifests": [
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 951,
         "digest": "sha256:572010bf16f05b153466dedfa4014a658b0ccbbbe36f544a6e7a7d6d445e0867",
         "platform": {
            "architecture": "amd64",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 1158,
         "digest": "sha256:f5ca6de76b302eff265ac315f26be31b458ac7e20004b4da9a08ce10c6eada34",
         "platform": {
            "architecture": "arm64",
            "os": "linux",
            "variant": "v8"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 1158,
         "digest": "sha256:1ebd274f6a06cd5b5ab85ed1d4e5da1c41a68f69d952f1725ea51a7366c95ede",
         "platform": {
            "architecture": "ppc64le",
            "os": "linux"
         }
      },
      {
         "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
         "size": 1158,
         "digest": "sha256:bc1f54d2015114bf177520d2c0a7e85e40b81741f051d163d3912a7391b99733",
         "platform": {
            "architecture": "s390x",
            "os": "linux"
         }
      }
   ]
}
commented

I guess it must be DockerHub's CI Server's temporary failure it happened once before