You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I am new to the buildpack and want to use the buildpack inside the CI process in the Kubernetes cluster, but when I do it, I come up with some questions.
I know that in the cluster, you suggest we use lifecycle/creator, but sInce the pack cli is so convenient, we don't need to run the builder image by ourselves and we don't have the docker runtime inside the Kubernetes now, I wonder if pack cli now supports using without using docker daemon? Or does pack cli support using podman purely?
I followed the Building on podman section in the official document and run buildpack with podman successfully in the local environment. Then I try to reproduce the same thing in the container.
I run a container, mount the docker socket, install podman, enable the podman socket via podman system service, and set DOCKER_HOST=podman.sock, I hope it should work like the local one. However, buildpack now uses podman to pull the run image and builder image but it exports the built application image to the docker daemon instead of the podman, which is really strange. Could you tell me why this case?
reacted with thumbs up emoji reacted with thumbs down emoji reacted with laugh emoji reacted with hooray emoji reacted with confused emoji reacted with heart emoji reacted with rocket emoji reacted with eyes emoji
-
Hello teams,
I am new to the buildpack and want to use the buildpack inside the CI process in the Kubernetes cluster, but when I do it, I come up with some questions.
I know that in the cluster, you suggest we use lifecycle/creator, but sInce the pack cli is so convenient, we don't need to run the builder image by ourselves and we don't have the docker runtime inside the Kubernetes now, I wonder if pack cli now supports using without using docker daemon? Or does pack cli support using podman purely?
I followed the Building on podman section in the official document and run buildpack with podman successfully in the local environment. Then I try to reproduce the same thing in the container.
I run a container, mount the docker socket, install podman, enable the podman socket via podman system service, and set DOCKER_HOST=podman.sock, I hope it should work like the local one. However, buildpack now uses podman to pull the run image and builder image but it exports the built application image to the docker daemon instead of the podman, which is really strange. Could you tell me why this case?
Beta Was this translation helpful? Give feedback.
All reactions