-
Notifications
You must be signed in to change notification settings - Fork 283
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Failure building samples with podman
#1995
Comments
Hi @abitrolly Did you try this? |
@jjbustamante hi. Yea, I missed the notice. What there is an "if" in "If using a The build progresses a bit futher, but still fails.
|
Interesting, maybe our samples code is broken. Did you try building some other app with a paketo builder maybe?
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 building with |
I am not sure about what you mean by "start the podman", that can not be part of a container because it is used to manage them. and as an external dependency, that seem worse than relying on Docker whose socket is theorically installed automatically with it. That's why i think the proposition done with my RFC is interesting, it allows pack to became standalone. |
This command starts
|
Sure, but that seem a strange demand, because pack was initally meant to work with Docker, this command in Podman exists to ensure compatibility because Docker was the de facto standard. But which tools pack should support ? And so check if they exists, etc. |
No, however in some case the lifecycle does not call the socket and rely on other mecanisms (volume mounted in the container running the lifecycle or direct sending of image in distant registry). |
I would vote for https://github.com/GoogleContainerTools/kaniko |
@abitrolly I think we have several issues with the samples applications (we now we need to work on them), but If I am not wrong, |
From the other side I believe some issue should be left open on documentation site too. |
Why ? It seem able to handle only dockerfile, in my opinion that does not fit the purpose of pack. |
|
Podman is rootless and daemonless too, it has a socket mode only to be compatible with tools which rely on the Docker socket. That's why, there is the RFC to include podman as a library to make pack standalone, rootless and daemonless. However the purpose of Kaniko is to build image from a dockerfile, in a containerised way (as pack, but pack and buildpacks are more flexible). So Kaniko is not meant to run container (it's probably possible to twist it to do so as it containerize things, but that would be weird). Beside that, Podman is meant to manage container, as an equivalent of docker, therefore i believe that Podman is a better choice. |
Summary
Building with
podman
as described here https://buildpacks.io/docs/app-developer-guide/building-on-podman/ doesn't work as expected.Reproduction
Steps
Current behavior
Expected behavior
No errors.
Environment
pack info
docker info
The text was updated successfully, but these errors were encountered: