Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

'image not known' for 'podman save' with arm64 image #10835

Closed
bkueng opened this issue Jul 1, 2021 · 3 comments · Fixed by #10844
Closed

'image not known' for 'podman save' with arm64 image #10835

bkueng opened this issue Jul 1, 2021 · 3 comments · Fixed by #10844
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.

Comments

@bkueng
Copy link

bkueng commented Jul 1, 2021

Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)

/kind bug

Description
podman save fails with image not known error when used for an arm64 image on amd64.
If the image is amd64, the command works as expected.

Steps to reproduce the issue:

  1. create a Dockerfile:
FROM arm64v8/ubuntu
  1. podman build . -t arm64-test

  2. podman save arm64-test > output.image
    Error: arm64-test: image not known

podman inspect arm64-test
[
    {
        "Id": "8707eaf216364b381d33fb63c3d9ee533c4c783fb0eee0282fa6f35386a0366f",
        "Digest": "sha256:3f7c2c6e153e218a10ff78b3868811795fa09cc5d01be28296390ac75ab018b0",
        "RepoTags": [
            "localhost/arm64-test:latest",
            "docker.io/arm64v8/ubuntu:latest"
        ],
        "RepoDigests": [
            "docker.io/arm64v8/ubuntu@sha256:3f7c2c6e153e218a10ff78b3868811795fa09cc5d01be28296390ac75ab018b0",
            "docker.io/arm64v8/ubuntu@sha256:4dbf156b12d531d688bfe209a582ce93bbed7348406be4075f07ca31c53a39f1",
            "localhost/arm64-test@sha256:3f7c2c6e153e218a10ff78b3868811795fa09cc5d01be28296390ac75ab018b0",
            "localhost/arm64-test@sha256:4dbf156b12d531d688bfe209a582ce93bbed7348406be4075f07ca31c53a39f1"
        ],
...

Interestingly, using the ID works:
podman save 8707eaf216364b381d33fb63c3d9ee533c4c783fb0eee0282fa6f35386a0366f > output.image

Output of podman version:

Version:      3.2.1
API Version:  3.2.1
Go Version:   go1.16.3
Built:        Mon Jun 14 21:12:29 2021
OS/Arch:      linux/amd64

Output of podman info --debug:

host:
  arch: amd64
  buildahVersion: 1.21.0
  cgroupControllers: []
  cgroupManager: systemd
  cgroupVersion: v2
  conmon:
    package: conmon-2.0.27-2.fc34.x86_64
    path: /usr/bin/conmon
    version: 'conmon version 2.0.27, commit: '
  cpus: 12
  distribution:
    distribution: fedora
    version: "34"
  eventLogger: journald
  hostname: bumblebee
  idMappings:
    gidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
    uidmap:
    - container_id: 0
      host_id: 1000
      size: 1
    - container_id: 1
      host_id: 100000
      size: 65536
  kernel: 5.12.12-300.fc34.x86_64
  linkmode: dynamic
  memFree: 15568211968
  memTotal: 33167806464
  ociRuntime:
    name: crun
    package: crun-0.20.1-1.fc34.x86_64
    path: /usr/bin/crun
    version: |-
      crun version 0.20.1
      commit: 0d42f1109fd73548f44b01b3e84d04a279e99d2e
      spec: 1.0.0
      +SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
  os: linux
  remoteSocket:
    path: /run/user/1000/podman/podman.sock
  security:
    apparmorEnabled: false
    capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
    rootless: true
    seccompEnabled: true
    seccompProfilePath: /usr/share/containers/seccomp.json
    selinuxEnabled: true
  serviceIsRemote: false
  slirp4netns:
    executable: /usr/bin/slirp4netns
    package: slirp4netns-1.1.9-1.fc34.x86_64
    version: |-
      slirp4netns version 1.1.8+dev
      commit: 6dc0186e020232ae1a6fcc1f7afbc3ea02fd3876
      libslirp: 4.4.0
      SLIRP_CONFIG_VERSION_MAX: 3
      libseccomp: 2.5.0
  swapFree: 23142043648
  swapTotal: 25270673408
  uptime: 71h 20m 24.8s (Approximately 2.96 days)
registries:
  search:
  - registry.fedoraproject.org
  - registry.access.redhat.com
  - docker.io
  - quay.io
store:
  configFile: /home/beat/.config/containers/storage.conf
  containerStore:
    number: 16
    paused: 0
    running: 0
    stopped: 16
  graphDriverName: overlay
  graphOptions:
    overlay.mount_program:
      Executable: /usr/bin/fuse-overlayfs
      Package: fuse-overlayfs-1.5.0-1.fc34.x86_64
      Version: |-
        fusermount3 version: 3.10.4
        fuse-overlayfs: version 1.5
        FUSE library version 3.10.4
        using FUSE kernel interface version 7.31
  graphRoot: /home/beat/.local/share/containers/storage
  graphStatus:
    Backing Filesystem: extfs
    Native Overlay Diff: "false"
    Supports d_type: "true"
    Using metacopy: "false"
  imageStore:
    number: 1022
  runRoot: /run/user/1000
  volumePath: /home/beat/.local/share/containers/storage/volumes
version:
  APIVersion: 3.2.1
  Built: 1623697949
  BuiltTime: Mon Jun 14 21:12:29 2021
  GitCommit: ""
  GoVersion: go1.16.3
  OsArch: linux/amd64
  Version: 3.2.1

Package info (e.g. output of rpm -q podman or apt list podman):

podman-3.2.1-1.fc34.x86_64
@openshift-ci openshift-ci bot added the kind/bug Categorizes issue or PR as related to a bug. label Jul 1, 2021
@vrothberg
Copy link
Member

Thanks for reaching out, @bkueng! Any chance you can try the latest Podman v3.2.2? We fixed a number of issues in the multi-arch space.

@vrothberg
Copy link
Member

Nope, I can reproduce.

vrothberg added a commit to vrothberg/libpod that referenced this issue Jul 2, 2021
Pull in fixes for local image lookups.

Fixes: containers#10835
Signed-off-by: Valentin Rothberg <[email protected]>
@bkueng
Copy link
Author

bkueng commented Jul 5, 2021

Thanks for the quick fix

learnitall referenced this issue in learnitall/benchmark-wrapper Jul 19, 2021
Having issues with podman recognizing multi-arch builds from buildah
@github-actions github-actions bot added the locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments. label Sep 21, 2023
@github-actions github-actions bot locked as resolved and limited conversation to collaborators Sep 21, 2023
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Labels
kind/bug Categorizes issue or PR as related to a bug. locked - please file new issue/PR Assist humans wanting to comment on an old issue or PR with locked comments.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants