Podman not working with

[matzew]

Trying the getting started from the initial README, I am getting errors, based on my podman CLI

pack build my-app-image --builder heroku/builder:22 --path node-js-getting-started

Here I get this ERROR:

ERROR: failed to build: failed to fetch builder image 'index.docker.io/heroku/builder:22': Cannot connect to the Docker daemon at unix:///var/run/docker.sock. Is the docker daemon running?

and for docker version command I am getting:

Client:       Podman Engine
Version:      4.9.3
API Version:  4.9.3
Go Version:   go1.21.7
Built:        Mon Feb 19 16:41:34 2024
OS/Arch:      linux/amd64

The pack CLI is this one:

pack --version
0.32.1+git-b14250b.build-5241

[edmorley]

@matzew Hi! Thank you for filing this.

Does the build work if you follow the steps here?
https://buildpacks.io/docs/for-app-developers/how-to/special-cases/build-on-podman/

I wonder if Pack CLI should add a special case to the error handling here, and if podman is detected on PATH, supplement the error message with a "If you are using Podman, see the docs here: link" note? (If you think this might be useful, would you mind opening a feature request upstream here: https://github.com/buildpacks/pack/issues/new/choose ?)

[schneems]

I was able to get pack build to use podman following those instructions, however it seems to have different behavior than docker regarding target architecture

$ podman machine init --cpus=2 --disk-size=30 --memory=8192

Downloading VM image: fedora-coreos-39.20240309.2.0-qemu.aarch64.qcow2.xz [===>--------------] 150.4MiB / 624.0MiB
Downloading VM image: fedora-coreos-39.20240309.2.0-qemu.aarch64.qcow2.xz [===>--------------] 154.4MiB / 624.0MiB
Downloading VM image: fedora-coreos-39.20240309.2.0-qemu.aarch64.qcow2.xz: done
Extracting compressed file: podman-machine-default_fedora-coreos-39.20240309.2.0-qemu.aarch64.qcow2: done
Image resized.
Machine init complete
To start your machine run:

	podman machine start

$ podman machine start

Starting machine "podman-machine-default"
Waiting for VM ...

Mounting volume... /Users:/Users
Mounting volume... /private:/private
Mounting volume... /var/folders:/var/folders

This machine is currently configured in rootless mode. If your containers
require root permissions (e.g. ports < 1024), or if you run into compatibility
issues with non-podman clients, you can switch using the following command:

        podman machine set --rootful

API forwarding listening on: /Users/rschneeman/.local/share/containers/podman/machine/qemu/podman.sock

The system helper service is not installed; the default Docker API socket
address can't be used by podman. If you would like to install it, run the following commands:

        sudo /opt/homebrew/Cellar/podman/4.9.3/bin/podman-mac-helper install
        podman machine stop; podman machine start

                You can still connect Docker API clients by setting DOCKER_HOST using the
following command in your terminal session:

        export DOCKER_HOST='unix:///Users/rschneeman/.local/share/containers/podman/machine/qemu/podman.sock'

Machine "podman-machine-default" started successfully
⛄️ 3.1.4 🚀 /tmp/node-js-getting-started (main)
$ ssh-add -k "$HOME/.ssh/podman-machine-default"
Identity added: /Users/rschneeman/.ssh/podman-machine-default ([email protected])
⛄️ 3.1.4 🚀 /tmp/node-js-getting-started (main)
$ podman system connection default podman-machine-default-root
⛄️ 3.1.4 🚀 /tmp/node-js-getting-started (main)
$ echo $(podman system connection ls --format="{{.URI}}" | grep root)
ssh://[email protected]:51365/run/podman/podman.sock
⛄️ 3.1.4 🚀 /tmp/node-js-getting-started (main)
$ export DOCKER_HOST="$(podman system connection ls --format="{{.URI}}" | grep root)"
⛄️ 3.1.4 🚀 /tmp/node-js-getting-started (main)
$ pack build my-image-name --path .
<redacted>
444766c92ef8: Download complete
7f17d068b167: Download complete
dbccd75cef00: Download complete
61dbc24dc4d4: Download complete
bccd10f490ab: Download complete
8a330204b8db: Download complete
7a7fa869f0e4: Download complete
182afb1fe5dc: Download complete
139eebe90b6d: Download complete
a67d576c0e44: Download complete
42d2e2757aac: Download complete
3978337195e2: Download complete
761c665a3f8e: Download complete
ad3ab113497d: Download complete
dfc596d4d938: Download complete
99d5723b6fc7: Download complete
3104e01b3ad1: Download complete
4f4055a94789: Download complete
d5c923b3cc1f: Download complete
37f22f2ad5c5: Download complete
cfb02d304230: Download complete
45100f0f762f: Download complete
fb77ecde3bf8: Download complete
0941a84b960e: Download complete
074e97169bf0: Download complete
2f68ba45cd78: Download complete
4eb0cb8403eb: Download complete
c2a991d41875: Download complete
4924da7d0d7f: Download complete
dcc7df304966: Download complete
b9f6de2761b9: Download complete
4f4fb700ef54: Download complete
1dc2c7310096: Download complete
dbccd75cef00: Already exists
7f17d068b167: Already exists
bccd10f490ab: Already exists
9dd2c54aa040: Download complete
a4a3aca6a3b7: Download complete
340f584f56f1: Download complete
===> ANALYZING
Image with name "my-image-name" not found
Image with name "heroku/heroku:22-cnb" not found
===> DETECTING
======== Output: heroku/[email protected] ========
No Python project files found (such as requirements.txt).
======== Results ========
fail: heroku/[email protected]
pass: heroku/[email protected]
======== Results ========
pass: heroku/[email protected]
skip: heroku/[email protected]
pass: heroku/[email protected]
pass: heroku/[email protected]
pass: heroku/[email protected]
Resolving plan... (try #1)
fail: heroku/[email protected] provides unused ruby
Resolving plan... (try #2)
skip: heroku/[email protected] provides unused jdk
fail: heroku/[email protected] provides unused ruby
======== Error: heroku/[email protected] ========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64"}]
======== Error: heroku/[email protected] ========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64"}]
======== Error: heroku/[email protected] ========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64"}]
======== Results ========
err:  heroku/[email protected]
err:  heroku/[email protected]
err:  heroku/[email protected]
pass: heroku/[email protected]
======== Error: heroku/[email protected] ========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64"}]
======== Error: heroku/[email protected] ========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64"}]
======== Error: heroku/[email protected] ========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64"}]
======== Results ========
err:  heroku/[email protected]
err:  heroku/[email protected]
err:  heroku/[email protected]
pass: heroku/[email protected]
======== Error: heroku/[email protected] ========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64"}]
======== Error: heroku/[email protected] ========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64"}]
======== Error: heroku/[email protected] ========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64"}]
======== Results ========
err:  heroku/[email protected]
err:  heroku/[email protected]
err:  heroku/[email protected]
pass: heroku/[email protected]
======== Error: heroku/[email protected] ========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64"}]
======== Error: heroku/[email protected] ========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64"}]
======== Results ========
err:  heroku/[email protected]
err:  heroku/[email protected]
skip: heroku/[email protected]
pass: heroku/[email protected]
pass: heroku/[email protected]
======== Error: heroku/[email protected] ========
unable to satisfy target os/arch constraints; run image: {"os":"linux","arch":"arm64"}, buildpack: [{"os":"linux","arch":"amd64"}]
======== Results ========
err:  heroku/[email protected]
pass: heroku/[email protected]
======== Results ========
pass: heroku/[email protected]
fail: heroku/[email protected]
pass: heroku/[email protected]
======== Results ========
pass: heroku/[email protected]
fail: heroku/[email protected]
pass: heroku/[email protected]
======== Results ========
pass: heroku/[email protected]
fail: heroku/[email protected]
pass: heroku/[email protected]
======== Results ========
pass: heroku/[email protected]
pass: heroku/[email protected]
Resolving plan... (try #1)
fail: heroku/[email protected] provides unused go
======== Output: heroku/[email protected] ========
No PHP project files found.
======== Results ========
fail: heroku/[email protected]
pass: heroku/[email protected]
ERROR: No buildpack groups passed detection.
ERROR: failed to detect: buildpack(s) failed with err
ERROR: failed to build: executing lifecycle: failed with status code: 21