如何使用docker desktop 下载x86、amd64、arm64 镜像？

朴灿烈づ我的快乐病毒、 2022-09-12 14:56 578阅读 0赞

如何使用docker desktop 下载x86、amd64、arm64 镜像？

  • 环境
  • 修改配置
  • 重启docker后下载镜像
  • 验证镜像架构

环境

在这里插入图片描述

修改配置

官网地址，开启 Docker CLI 的实验特性
docker desktop 的Preferences=>>Docker Engine
experimental 的值设置成 true，意思是：开启manifest实验特性

  1. {
  3.   "registry-mirrors": [
  4.     "https://registry.cn-hangzhou.aliyuncs.com"
  5.   ],
  6.   "insecure-registries": [
  7.     "0.0.0.0/0",
  8.     "dockerhub.kubesphere.local:443"
  9.   ],
  10.   "debug": true,
  11.   "experimental": true
  12. }

重启docker后下载镜像

–platform=arm64指定CPU平台架构的镜像

  1. ➜  ~ docker pull --platform=arm64 nginx:latest
  2. latest: Pulling from library/nginx
  3. d10c227306ce: Pull complete
  4. 6d7f45405386: Pull complete
  5. 1b5147f94884: Pull complete
  6. 52ae3a597441: Pull complete
  7. 3ce50094efa7: Pull complete
  8. 7bf647869efa: Pull complete
  9. Digest: sha256:853b221d3341add7aaadf5f81dd088ea943ab9c918766e295321294b035f3f3e
  10. Status: Downloaded newer image for nginx:latest
  11. docker.io/library/nginx:latest

验证镜像架构

docker manifest inspect —insecure nginx:latest

  1. ➜  ~ docker manifest inspect --insecure nginx:latest
  2. ^[{
  4.    "schemaVersion": 2,
  5.    "mediaType": "application/vnd.docker.distribution.manifest.list.v2+json",
  6.    "manifests": [
  7.       {
  9.          "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
  10.          "size": 1570,
  11.          "digest": "sha256:6fe11397c34b973f3c957f0da22b09b7f11a4802e1db47aef54c29e2813cc125",
  12.          "platform": {
  14.             "architecture": "amd64",
  15.             "os": "linux"
  16.          }
  17.       },
  18.       {
  20.          "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
  21.          "size": 1570,
  22.          "digest": "sha256:f6d65972ac54772c5f6b952e396aad3e516fcb250cd5825b98a33a82286c91c2",
  23.          "platform": {
  25.             "architecture": "arm",
  26.             "os": "linux",
  27.             "variant": "v5"
  28.          }
  29.       },
  30.       {
  32.          "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
  33.          "size": 1570,
  34.          "digest": "sha256:8f4514d178b1f178fa04a5307695a7477af68bf95e78ec0ec6172a7ab06c30a2",
  35.          "platform": {
  37.             "architecture": "arm",
  38.             "os": "linux",
  39.             "variant": "v7"
  40.          }
  41.       },
  42.       {
  44.          "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
  45.          "size": 1570,
  46.          "digest": "sha256:f68304ec388f969b0929d695a05a36ecdb3665009258631cb898ba046963e72a",
  47.          "platform": {
  49.             "architecture": "arm64",
  50.             "os": "linux",
  51.             "variant": "v8"
  52.          }
  53.       },
  54.       {
  56.          "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
  57.          "size": 1570,
  58.          "digest": "sha256:0b5b438edb8be60c445a89a4c9043681ea16ef1cfcc0e9c168c059d76fb8e04e",
  59.          "platform": {
  61.             "architecture": "386",
  62.             "os": "linux"
  63.          }
  64.       },
  65.       {
  67.          "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
  68.          "size": 1570,
  69.          "digest": "sha256:3e0cbe127ddfb82dde1e6c150199cfdfdc35c6a4a3cb7b7ff5f8c09e47df00be",
  70.          "platform": {
  72.             "architecture": "mips64le",
  73.             "os": "linux"
  74.          }
  75.       },
  76.       {
  78.          "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
  79.          "size": 1570,
  80.          "digest": "sha256:2472887e70008a6ed87a004c5c70e5fbc6e2e47aeac3d76d149669a4119f4bd6",
  81.          "platform": {
  83.             "architecture": "ppc64le",
  84.             "os": "linux"
  85.          }
  86.       },
  87.       {
  89.          "mediaType": "application/vnd.docker.distribution.manifest.v2+json",
  90.          "size": 1570,
  91.          "digest": "sha256:ef218d58b531ffaf0702b4d8f14501e6d84b25efe384171eb0e839a2f662e676",
  92.          "platform": {
  94.             "architecture": "s390x",
  95.             "os": "linux"
  96.          }
  97.       }
  98.    ]
  99. }

参考文章

发表评论

表情：
评论列表 （有 0 条评论，578人围观）

还没有评论，来说两句吧...

相关阅读

    相关 X86和X86_64和AMD64的由来

    为什么叫X86和X86\_64和AMD64 为什么大家叫x86为32位系统呢 相信大家在大学里面有很多人都玩过8086(微处理器)，这是一个可编程的系统，他是由intel

    怼烎@怼烎@/ 0 赞/ 107 阅读