-
-
Notifications
You must be signed in to change notification settings - Fork 150
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
Would like ability to add additional args to podman build
#69
Comments
I would like to note that while implementing this, I did notice that there wasn't a mechanism to test several of the other suboptions provided to build in the The following playbook executed correctly with that installed:
|
@jharmison-redhat thanks, |
@jharmison-redhat I included this change, needed it for cgroups args of podman build in #83 |
Fix idempotency issues in podman_container Add creating workdir, buildah issue: containers/buildah#2475 Fix #68 Fix #69 Should help to #80 as well, but will be handled separately.
Was on PTO last week and pretty busy juggling the week prior, glad you were able to get this in. Thanks! |
Is this a BUG REPORT or FEATURE REQUEST? (leave only one on its own line)
/kind feature
Description
Would like the ability to provide arbitrary args to
podman build
invocation through the command constructor, or support for more args supported by podman. In my particular use case, I need to provideulimit
args forRUN
statements in a Dockerfile, which is supported bypodman build
natively.Steps to reproduce the issue:
Include a
RUN
statement in your Dockerfile that requires a ulimit other than the default of 1024.Use
podman build /path --ulimit=nofile=4096:4096 -t imagename
Attempt to find a way to do the same with
containers.podman.podman_image
.Describe the results you received:
podman build
: Works as expectedcontainers.podman.podman_image
: Thepodman build
args are constructed incrementally from a fixed set of options, with no ability to specify either ulimit or arbitrary build args.Describe the results you expected:
One of the following:
containers.podman.podman_image
provides either a ulimit arg, as a suboption tobuild
or in some other useful way.containers.podman.podman_image
provides a way to pass arbitrary args on invocation ofpodman build
, allowing me to use the--ulimit
arg.Additional information you deem important (e.g. issue happens only occasionally):
I can implement, but would like to know what the project's preferred implementation would be.
Output of
ansible --version
:Output of
podman version
:Output of
podman info --debug
:Package info (e.g. output of
rpm -q podman
orapt list podman
):Playbook you run with ansible (e.g. content of
playbook.yaml
):Command line and output of ansible run with high verbosity:
Additional environment details (AWS, VirtualBox, physical, etc.):
Physical runs on my host. This is a small example to demonstrate the particulars of my use case, with my actual implementation being a complex playbook with many roles, a custom library, etc.
Dockerfile contents:
install-script contents:
Output of
podman build
running with--ulimit
arg:The text was updated successfully, but these errors were encountered: