Starting a container with the --platform option explicitly provided rather than inferred from the container image seems to add a delay to starting the container.
I suspect this is due to unnecessary network requests. When I disconnect my Wi-Fi, the container start time decreases, probably because it skips whatever network request(s) is causing the delay.
Steps to reproduce the issue
$ time podman run --rm -it alpine:3 arch
aarch64
... 0.03s user 0.02s system 11% cpu 0.433 total
$ time podman run --rm -it --platform=linux/arm64 alpine:3 arch
aarch64
... 0.04s user 0.02s system 3% cpu 1.858 total
Describe the results you received
With the --platform flag the time is 4.5x as long in the above example.
Describe the results you expected
There should be no difference in container start time when explicitly specifying the platform.
Issue Description
Starting a container with the
--platform
option explicitly provided rather than inferred from the container image seems to add a delay to starting the container.I suspect this is due to unnecessary network requests. When I disconnect my Wi-Fi, the container start time decreases, probably because it skips whatever network request(s) is causing the delay.
Steps to reproduce the issue
Describe the results you received
With the
--platform
flag the time is 4.5x as long in the above example.Describe the results you expected
There should be no difference in container start time when explicitly specifying the platform.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
No response
Additional information
No response