Ask questionsno matching manifest for linux/arm64/unknown
<!-- If you are reporting a new issue, make sure that we do not have any duplicates already open. You can ensure this by searching the issue list for this repository. If there is a duplicate, please close your issue and add a comment to the existing issue instead.
If you suspect your issue is a bug, please edit your issue description to include the BUG REPORT INFORMATION shown below. If you fail to provide this information within 7 days, we cannot debug your issue and will close it. We will, however, reopen it if you later provide the information.
For more information about reporting issues, see https://github.com/moby/moby/blob/master/CONTRIBUTING.md#reporting-other-issues
The GitHub issue tracker is for bug reports and feature requests. General support for docker can be found at the following locations:
General support for moby can be found at the following locations:
Use the commands below to provide key information from your environment: You do NOT have to include this information if this is a FEATURE REQUEST -->
When pulling any image it always fails with
no matching manifest for linux/arm64/unknown in the manifest list entries even if there is an image available which clearly runs on the platform.
It seems that there is a bug in the platform detection for this CPU. And there doesn't seem to be a way to override the detected platform on the docker daemon?
<!-- Briefly describe the problem you are having in a few paragraphs. -->
Steps to reproduce the issue:
docker pull k8s.gcr.io/pause:3.1 or
docker pull traefik:1.7.9 (or any other image).
Describe the results you received:
3.1: Pulling from pause no matching manifest for linux/arm64/unknown in the manifest list entries
1.7.9: Pulling from library/traefik 1.7.9: Pulling from library/traefik no matching manifest for linux/arm64/unknown in the manifest list entries
Describe the results you expected:
Matching images get pulled.
Additional information you deem important (e.g. issue happens only occasionally):
# cat /proc/cpuinfo Processor : AArch64 Processor rev 4 (aarch64) processor : 0 processor : 1 processor : 2 processor : 3 Features : fp asimd aes pmull sha1 sha2 crc32 CPU implementer : 0x41 CPU architecture: AArch64 CPU variant : 0x0 CPU part : 0xd03 CPU revision : 4 Hardware : sun50iw1p1
Pulling the images with
docker pull --platform arm64 (experimental feature) successfully pulls the images and the images are then able to be executed. It seems that the platform detection fails.
Version: 18.09.6 API version: 1.39 Go version: go1.10.8 Git commit: 481bc77 Built: Sat May 4 02:43:11 2019 OS/Arch: linux/arm64 Experimental: false Server: Docker Engine - Community Engine: Version: 18.09.6 API version: 1.39 (minimum version 1.12) Go version: go1.10.8 Git commit: 481bc77 Built: Sat May 4 02:00:10 2019 OS/Arch: linux/arm64 Experimental: true
Running: 3 Paused: 0 Stopped: 0 Images: 5 Server Version: 18.09.6 Storage Driver: aufs Root Dir: /var/lib/docker/aufs Backing Filesystem: extfs Dirs: 19 Dirperm1 Supported: true Logging Driver: json-file Cgroup Driver: cgroupfs Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local logentries splunk syslog Swarm: inactive Runtimes: runc Default Runtime: runc Init Binary: docker-init containerd version: bb71b10fd8f58240ca47fbb579b9d1028eea7c84 runc version: 2b18fe1d885ee5083ef9f0838fee39b62d653e30 init version: fec3683 Security Options: apparmor seccomp Profile: default Kernel Version: 3.10.107-pine64 Operating System: Ubuntu 16.04.6 LTS OSType: linux Architecture: aarch64 CPUs: 4 Total Memory: 1.941GiB Name: master1 ID: VTUU:MTEC:S2GO:K4X2:TUO7:GN2T:HMGV:COZP:S4CR:GCMX:6H65:SO6J Docker Root Dir: /var/lib/docker Debug Mode (client): false Debug Mode (server): false Registry: https://index.docker.io/v1/ Labels: Experimental: true Insecure Registries: 127.0.0.0/8 Registry Mirrors: http://192.168.242.1:5000/ Live Restore Enabled: false Product License: Community Engine WARNING: No swap limit support
Additional environment details (AWS, VirtualBox, physical, etc.):
Physical ARM board on Armbian:
Answer questions tobru
Thanks for taking care!
It really looks like the Kernel is too old for version 18.09 or there is a bug somewhere as with older versions it used to work. Unfortunately I didn't note the version when it worked, I've updated lately to 18.09. It worked about a year ago, never faced this
no matching manifest for... back then: Same boards, same distro, same Kernel. There must have been changes since them which introduced new features and of course: a new bug.