3 ms·
My Podman starts containers in arch x86-64-v3 with rosetta on for 27 seconds which Docker does it in 9s. I wonder what's wrong. I've already upgraded Mac to Tah
by p0w3n3d 8mo ago
My Podman starts containers in arch x86-64-v3 with rosetta on for 27 seconds which Docker does it in 9s. I wonder what's wrong. I've already upgraded Mac to Tahoe (which has x86-64-v3 support included into rosetta)
- cdrage 8mo agoAhhh, one of the reasons could be that Docker Desktop by default uses 50% of your RAM when they create their VM and the maximum amount of CPUs. Podman Desktop by default has a much lower RAM (4GB) + CPU usage (50% CPU). That's something that could be improved... I've opened up an issue: https://github.com/podman-desktop/podman-desktop/issues/16349 https://github.com/podman-desktop/podman-desktop/issues/1634... :)
- p0w3n3d 8mo agoNo I checked it against the amount of RAM. Podman with 8GB does not increase speed, Docker with 4GB is still 9s podman run 27->24 docker run 9.4->9.769 total (I increased limit in podman and decreased limit in docker). This happens with amd64 arch images (which I for some reason need in my work and cannot rebuild)
- cdrage 8mo agonow I'm curious why it's still slow even with the increase of ram + cpu, I'll sync up with the podman core team why it's benchmarking much faster in docker vs podman (assuming both are using rosetta 2 on your machine)
- newsoftheday 8mo ago> now I'm curious why it's still slow even with the increase of ram + cpu Because podman doesn't work as well as docker.
- p0w3n3d 8mo agoI have double checked if my rosetta is enabled. I also requrested using "apple virtualization" instead of libkrun
- p0w3n3d 8mo agoare you by any chance one of those Claw raging robots? really? created an issue?
- bootsmann 8mo ago(The poster works on podman for redhat)
- worthless-trash 8mo agoPretty sure this guy works in that project.
- bityard 8mo agoThere 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
- p0w3n3d 8mo agoI'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 } ]