-
-
Notifications
You must be signed in to change notification settings - Fork 1.1k
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
Change container builder from Docker to Buildah/Podman #606
Comments
Could you please share the errors you encounter when trying to build with Podman? |
$ alias docker=podman && make build BASE_IMAGE=registry.hub.docker.com/library/debian:stable NAME=phusion/debian-baseimage-docker
podman build --no-cache -t phusion/debian-baseimage-docker:focal-1.0.0-pre --build-arg BASE_IMAGE=registry.hub.docker.com/library/debian:stable --build-arg QEMU_ARCH=amd64 --platform
Error: flag needs an argument: --platform
make: *** [Makefile:26: build] Error 125 |
This Issue has been automatically marked as "stale" because it has not had recent activity (for 15 days). It will be closed if no further activity occurs. Thanks for the feedback. |
Due to the lack of activity in the last 5 days since it was marked as "stale", we proceed to close this Issue. Do not hesitate to reopen it later if necessary. |
You seem to be missing an argument, and thus it fails but unfortunately it's been a while since I have tried to build it via make, and should probably update it. It however should currently work when you pass in |
Details
There has been a recent trend moving away from Docker's original tooling, in favor of tooling with better OCI support. My suggestion is to update the tooling for building this container to something that could be either compatible with both Docker and OCI tooling (like Podman) or to add an option to use something like Buildah to build an OCI compatible container image.
Currently, the container is being built with Docker and fails to build with Podman (when using Podman-Docker aliasing).
The text was updated successfully, but these errors were encountered: