pack: Failure building samples with `podman`

Summary

Building with podman as described here https://buildpacks.io/docs/app-developer-guide/building-on-podman/ doesn’t work as expected.

Reproduction

Steps

git clone https://github.com/buildpacks/samples
export DOCKER_HOST="unix://$(podman info -f "{{.Host.RemoteSocket.Path}}")" 
podman system service -t 60 & pack build sample-app -p samples/apps/ruby-bundler/ -B cnbs/sample-builder:jammy

Current behavior

...
Copying blob fc454e27c1c6 skipped: already exists  
Copying config 5840b7958b done   | 
Writing manifest to image destination
===> ANALYZING
ERROR: failed to build: executing lifecycle: failed to create 'analyzer' container: Error response from daemon: make cli opts(): making volume mountpoint for volume /var/run/docker.sock: mkdir /var/run/docker.sock: permission denied

Expected behavior

No errors.

Environment

pack info

Pack:
  Version:  0.32.1+git-b14250b.build-5241
  OS/Arch:  linux/amd64

Default Lifecycle Version:  0.17.2

Supported Platform APIs:  0.3, 0.4, 0.5, 0.6, 0.7, 0.8, 0.9, 0.10, 0.11, 0.12

docker info

$ podman version
Client:       Podman Engine
Version:      4.7.2
API Version:  4.7.2
Go Version:   go1.21.1
Built:        Tue Oct 31 17:32:01 2023
OS/Arch:      linux/amd64

About this issue

Original URL
State: closed
Created 7 months ago
Comments: 15 (10 by maintainers)

Most upvoted comments

Interesting, maybe our samples code is broken. Did you try building some other app with a paketo builder maybe?

@jjbustamante hi. Yea, I missed the notice. What there is an “if” in “If using a socket connection”? Is it possible to use podman without the socket connection?

We’ve being discussing this RFC, you can see the detail here which I think it is want you want. right?

Right now it is not possible to run without the socket connection.

I cc @dvaumoron (he is working in the RFC) and @matejvasek because you are always involved with podman stuffs

jjbustamante on Nov 30, 2023