Support for pylero-cmd to be packaged as a docker container?

[Dannyb48]

Was looking to leverage pylero-cmd within one of our test executor containers but rather than building the dependencies into my container was wondering if Pylero has any plans of having a containerized offering? that could be layered into other containers?

[leelavg]

• Could be done with ease and can use ghcr itself to host the container
• Let me give a try, I'll also add an action to build container when a release is tagged or branched if required
• Btw, if you have any Red Hat family base images, we recently started copr builds as well

[waynesun09]

For base image we could consider the latest ubi9 images:
ubi9 base:
https://catalog.redhat.com/software/containers/ubi9/618326f8c0d15aff4912fe0b?container-tabs=gti

python 3.9 on ubi9:
https://catalog.redhat.com/software/containers/ubi9/python-39/61a61032bfd4a5234d59629e?container-tabs=gti

[leelavg]

• Ack, awaiting user info.
• I see the requirement as "layered into other containers", so not sure whether they want pylero to be installed at a specific path and then later be copied during a multi-stage build or pylero standalone.
• This is what I'm thinking, build the image with pylero installed in a venv and provide a way to copy the venv to any other container that already has python installed.

[Dannyb48]

@leelavg I apologize I may not be using appropriate terminology. I think initially I wanted to build my container that contained other tooling (golang tools) on top of a container that already had pylero in it. But that might not be best practice?

We could start with just a pylero-cmd/cli standalone in a container that I could easily do the following
docker/podman pull pylero-cmd
docker/podman run pylero-cmd list.