podman build --arch applies for base images #3261
Description
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind bug
Description
Since podman 3, building an image with --arch that is not the host architecture applies to base images pulled.
Steps to reproduce the issue:
- Create a Dockerfile with this content:
FROM alpine:latest AS builder
RUN echo "hello world"
FROM scratch
podman build --arch arm64 .on an x86_64 machine
Describe the results you received:
STEP 2: RUN echo "hello world"
exec container process `/bin/sh`: Exec format error
It pulls the aarch64 alpine image instead of the x86_64 one
Describe the results you expected:
I expect it to pull the host architecture base images and only tag the final image as arm64, just like podman 2. I need this flag to set the architecture of my cross-compiling images that are based on scratch and contain a single static binary which in this case is aarch64, built on an x86_64 host.
Additional information you deem important (e.g. issue happens only occasionally):
Output of podman version:
Version: 3.1.2
API Version: 3.1.2
Go Version: go1.15.11
Built: Tue May 11 15:53:47 2021
OS/Arch: linux/amd64
Output of podman info --debug:
host:
arch: amd64
buildahVersion: 1.20.1
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.0.27-2.fc33.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.0.27, commit: '
cpus: 8
distribution:
distribution: fedora
version: "33"
eventLogger: journald
hostname: ceres
idMappings:
gidmap:
- container_id: 0
host_id: 1009
size: 1
- container_id: 1
host_id: 165536
size: 65536
uidmap:
- container_id: 0
host_id: 1020
size: 1
- container_id: 1
host_id: 165536
size: 65536
kernel: 5.12.6-200.fc33.x86_64
linkmode: dynamic
memFree: 16190173184
memTotal: 33617817600
ociRuntime:
name: crun
package: crun-0.19.1-3.fc33.x86_64
path: /usr/bin/crun
version: |-
crun version 0.19.1
commit: 1535fedf0b83fb898d449f9680000f729ba719f5
spec: 1.0.0
+SYSTEMD +SELINUX +APPARMOR +CAP +SECCOMP +EBPF +CRIU +YAJL
os: linux
remoteSocket:
path: /run/user/1020/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
selinuxEnabled: true
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.1.9-1.fc33.x86_64
version: |-
slirp4netns version 1.1.9
commit: 4e37ea557562e0d7a64dc636eff156f64927335e
libslirp: 4.3.1
SLIRP_CONFIG_VERSION_MAX: 3
libseccomp: 2.5.0
swapFree: 12754870272
swapTotal: 12754870272
uptime: 2h 31m 13.48s (Approximately 0.08 days)
registries:
search:
- registry.fedoraproject.org
- registry.access.redhat.com
- docker.io
store:
configFile: /home/jens/.config/containers/storage.conf
containerStore:
number: 2
paused: 0
running: 0
stopped: 2
graphDriverName: overlay
graphOptions:
overlay.mount_program:
Executable: /usr/bin/fuse-overlayfs
Package: fuse-overlayfs-1.5.0-1.fc33.x86_64
Version: |-
fusermount3 version: 3.9.3
fuse-overlayfs: version 1.5
FUSE library version 3.9.3
using FUSE kernel interface version 7.31
graphRoot: /home/jens/.local/share/containers/storage
graphStatus:
Backing Filesystem: xfs
Native Overlay Diff: "false"
Supports d_type: "true"
Using metacopy: "false"
imageStore:
number: 23
runRoot: /run/user/1020
volumePath: /home/jens/.local/share/containers/storage/volumes
version:
APIVersion: 3.1.2
Built: 1620741227
BuiltTime: Tue May 11 15:53:47 2021
GitCommit: ""
GoVersion: go1.15.11
OsArch: linux/amd64
Version: 3.1.2
Package info (e.g. output of rpm -q podman or apt list podman):
podman-3.1.2-2.fc33.x86_64
Have you tested with the latest version of Podman and have you checked the Podman Troubleshooting Guide? (https://github.com/containers/podman/blob/master/troubleshooting.md)
Yes
Additional environment details (AWS, VirtualBox, physical, etc.):
also happens in the rc3 podman image that is on quay, docker behaves in the way i described as expected result