Make it possible to set entrypoint for working_container.

[Smeds]

Fixes #198

[TomasTomecek]

Nice, looking good!

Would you be interested in adding the parameter to documentation and writing a test case? If not, I can do that myself.

[Smeds]

Absolutely! I will put same time on documentation and testing later this week.

[Smeds]

Added some content and a simple test! But I must say that I don't really know every place where I should add entries for testing.

[TomasTomecek]

/packit build

[TomasTomecek]

Thanks, looking good! This is fine for me. I'm gonna play with it a bit more tomorrow.

[packit-as-a-service]

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

• sudo yum install -y dnf-plugins-core on RHEL 8
• sudo dnf install -y dnf-plugins-core on Fedora
• dnf copr enable packit/ansible-community-ansible-bender-232
• And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

[TomasTomecek]

/packit build

[packit-as-a-service]

Based on your Packit configuration the settings of the packit/ansible-community-ansible-bender-232 Copr project would need to be updated as follows:

field	old value	new value
chroots	['fedora-31-x86_64']	['fedora-31-x86_64', 'fedora-30-x86_64']

Packit was unable to update the settings above as it is missing admin permissions on the packit/ansible-community-ansible-bender-232 Copr project.

To fix this you can do one of the following:

• Grant Packit admin permissions on the packit/ansible-community-ansible-bender-232 Copr project on the permissions page.
• Change the above Copr project settings manually on the settings page to match the Packit configuration.
• Update the Packit configuration to match the Copr project settings.

Please re-trigger the build, once the issue above is fixed.

[TomasTomecek]

I played with it locally a bit and found two issues which I fixed and pushed a commit to your branch.

Can someone verify this works correctly? I looked into entrypoint details and the thing is that buildah doesn't seem to use that value for a working container:

$ man buildah-config
...
       --entrypoint "command" | '["command", "arg1", ...]'

       Set  the  entry point for containers based on any images which will be built using the specified container. buildah supports two formats for entrypoint.  It can be specified as a
       simple string, or as a array of commands.

       Note: When the entrypoint is specified as a string, container runtimes will ignore the cmd value of the container image.  However if you use the array form, then the cmd will  be
       appended onto the end of the entrypoint cmd and be executed together.

Or maybe I don't understand the manpage.

[TomasTomecek]

/packit build

[TomasTomecek]

/packit build

[packit-as-a-service]

Congratulations! One of the builds has completed. 🍾

You can install the built RPMs by following these steps:

• sudo yum install -y dnf-plugins-core on RHEL 8
• sudo dnf install -y dnf-plugins-core on Fedora
• dnf copr enable packit/ansible-community-ansible-bender-232
• And now you can install the packages.

Please note that the RPMs should be used only in a testing environment.

[TomasTomecek]

test failures are unrelated, merging

thank you for your contribution!