-
Notifications
You must be signed in to change notification settings - Fork 6
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
Published images do not include cpp #35
Comments
Thanks for reaching out, @iluminae ! @cevich @TomSweeneyRedHat looks like we need to add |
The image would grow by 48 MB. |
I mean there are enough users that want smaller images so adding more packages will not help for that. How common is the cpp functionality really? User can always build their own images with use quay.io/podman/stable as the base image to add any extra packages they want. |
That is a fair point but we need to balance size against a documented feature not working out of the box. |
I am in the camp that currently has to install cpp into the container to use it. In CI, this is unfortunate as I either have to maintain a bespoke build image or install cpp every time (and man is dnf slow). I just thought I would bring up that as supported it seemed out of place that it would not have it in there. |
Yeah it is fair to bring this up, if enough people want to use cpp syntax then it is certainly worth to have it in by default. |
IMHO it's not worth the extra space + dependencies. This is exactly why images are compose-able based on other images. |
wrt popularity of cpp use - anecdotally, its been quite critical to our success with podman - we have a highly parallelized ( |
I don't know why we have to have a small image for embedded podman versus functionality, given the choice I would go with functionality. We can look at other features to shrink the size, perhaps go back to fedora-minimal with dnf added. Can we remove timezone and language data? @iluminae Interested in opening a PR to add cpp? I am curios why the cpp package requires 48 Meg? |
@cevich and I chatted briefly in another thread somewhere. We discussed possibly adding a new "minimal" or "stripped down" image. One that would have just what we thought was the bare necessities. Then another image that is a bit more buff and would work for most people out of the box, but be bigger. My vote, I'd add CPP to the image, but not a strong vote. I would like to see us, when we have copious spare time, create a minimal image for Buildah, Podman, and Skopeo. That would be a fun little project. |
does it interest anyone to support a different edit: On second thought, that seems tough since we wire through CPPFLAGS in buildah |
Here is the PR if you guys want to just add |
I think supporting ucpp makes some sense, I wish we could use the same path. |
A friendly reminder that this issue had no activity for 30 days. |
Woops, lost track of this. Working on adding it now. |
Issue Description
the published images at quay.io/podman/stable (which I believe are created with
contrib/podmanimage/stable/Containerfile
) do not includecpp
. This is used automatically by podman to build Containerfiles that include the suffix.in
Steps to reproduce the issue
Steps to reproduce the issue
echo "FROM scatch" > Containerfile.in
podman run -v $PWD:/work -w /work quay.io/podman/stable podman build -f Containerfile.in .
Describe the results you received
Error: exec: "cpp": executable file not found in $PATH: .in support requires cpp to be installed
Describe the results you expected
Since Containerfile.in files are supported by podman, I expected this tool to be included. As a parallel, these images include ssh clients needed for podman to exec ssh, which is roughly the same.
podman info output
Podman in a container
Yes
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
Additional environment details
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: