Hacker News new | ask | show | jobs
by bityard 117 days ago
There is definitely something wrong with your setup. I can run an amd64 container on my Macbook Pro M3 in well under a second:

    [~]$ podman pull --arch=amd64 debian:13
    Resolved "debian" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
    Trying to pull docker.io/library/debian:13...
    Getting image source signatures
    Copying blob sha256:866771c43bf5eb77362eeeb163c0c825e194c2806d0b697028434e3b9c02f59d
    Copying config sha256:a3624ddeb711bef28c29e6de1502fc3ef9df132c220d1db5a121b2a1e2a74256
    Writing manifest to image destination
    a3624ddeb711bef28c29e6de1502fc3ef9df132c220d1db5a121b2a1e2a74256

    [~]$ time podman run --rm -ti debian:13 uname -m
    WARNING: image platform (linux/amd64) does not match the expected platform (linux/arm64)
    x86_64
    podman run --rm -ti debian:13 uname -m  0.03s user 0.02s system 9% cpu 0.456 total
1 comments

I've checked and there is no difference between podman and docker on my machine.

However when running a spring boot over eclipse-temurin:25-jdk-ubi10-minimal image there is this huge difference

  podman run   0.02s user 0.01s system 0% cpu 24.960 total
you can see the java app starting slowly. I've double checked that rosetta is enabled on podman.

  % podman machine inspect podman-machine-default
  ...

        "Rootful": true,
        "Rosetta": true
     }
  ]