-
Notifications
You must be signed in to change notification settings - Fork 17
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
Multiple pythons needed for podman-py testing #111
Conversation
Cirrus CI build successful. Image ID |
DO NOT USE c6391889636098048: The container images are getting "too big" due to the extra python versions. @jwhonce do any of your tests run in the container images or are VMs used exclusively? If so...I can limit the extra python bits to only installing in VMs and not the containers. |
@cevich I don't know, the cirrus.yaml has a container field. Does that mean the tests are only run in a container? (currently...) |
Sorry, I thought maybe you'd know off-hand. Taking a look in podman-py, I see the |
Let's try it this way: I moved most of the python bits into the VM-only list of installs. We'll need to confirm the images work with podman CI, but this will all but negate any container-image size concerns (unless it doesn't work)... |
Cirrus CI build successful. Image ID |
K, lessee if it works in podman. You're welcome to test |
Right, okay so we need some python stuffs in the containers then. Lemmie go into one manually where I can |
...oof, okay, no won't work. That said (and I remember we talked about this before), it seems like we need a custom image for the This does take quite a bit of effort to pull off, and we're in the middle of the. podman 4.0 crunch. Is a working containers/podman-py#160 necessary/critical for the 4.0 efforts? I can spend a little time on it today, since other folks are OOO - and I'm blocked on their help to move some items forward.... |
The |
Repos timed out, retrying... |
|
Still timing out. I don't get it. The other VM images build in < 10 minutes. WTH going on with the new one it taking so long. |
Found the problem...there was a |
AAAAAND if it ain't one thing...it's something else...and something else...and... |
Previously the VM images used for automation were generic/one-size-fits-all. However over time, various repos. have required numerous updates resulting in a great deal of bloat. To combat this, a dedicated VM image has been crafted for use just by this repo. Put this into use, and re-order tasks in `.cirrus.yml` to match more closely with the order of operations. Ref: containers/automation_images#111 Signed-off-by: Chris Evich <[email protected]>
Previously the VM images used for automation were generic/one-size-fits-all. However over time, various repos. have required numerous updates resulting in a great deal of bloat. To combat this, a dedicated VM image has been crafted for use just by this repo. Put this into use, and re-order tasks in `.cirrus.yml` to match more closely with the order of operations. Ref: containers/automation_images#111 Signed-off-by: Chris Evich <[email protected]>
Cirrus CI build successful. Image ID |
The one-size-fits-all approach is ever increasingly showing gaps and inefficiencies WRT CI for the `podman-py` repository. Rather than continue to increase the bloat of the golang-centric images, produce a dedicated image for this repo. This allows pre-installing/caching all the necessary python bits needed, avoiding the need to install them at runtime. It will require updates to the `podman-py` setup in order to make use of the new image effectively. Signed-off-by: Chris Evich <[email protected]>
@jwhonce update: The new image seems to work with podman-py containers/podman-py#161 but I got a bit delete-happy yanking python stuff out of the other images. That seems to have broke the docker-py testing we do in podman. So I'm putting the general Fedora image back the way it was, and we'll give the new set of images another go 'round... |
Cirrus CI build successful. Image ID |
Mainly this is to confirm some changes needed for the podman-py CI setup don't disrupt operations here. Ref: containers/automation_images#111 Signed-off-by: Chris Evich <[email protected]>
Mainly this is to confirm some changes needed for the podman-py CI setup don't disrupt operations here. Ref: containers/automation_images#111 Signed-off-by: Chris Evich <[email protected]>
Mainly this is to confirm some changes needed for the podman-py CI setup don't disrupt operations here. Ref: containers/automation_images#111 Signed-off-by: Chris Evich <[email protected]>
Mainly this is to confirm some changes needed for the podman-py CI setup don't disrupt operations here. Ref: containers/automation_images#111 Signed-off-by: Chris Evich <[email protected]>
This is necessary because both are pulled in by containers-common in the updates-testing repo. for F35. Since they will never be officially supported along with podman 4 in F35, ensure they're not present in any images. Signed-off-by: Chris Evich <[email protected]>
Mainly this is to confirm some changes needed for the podman-py CI setup don't disrupt operations here. Ref: containers/automation_images#111 Signed-off-by: Chris Evich <[email protected]>
Previously the VM images used for automation were generic/one-size-fits-all. However over time, various repos. have required numerous updates resulting in a great deal of bloat. To combat this, a dedicated VM image has been crafted for use just by this repo. Put this into use, and re-order tasks in `.cirrus.yml` to match more closely with the order of operations. Ref: containers/automation_images#111 Signed-off-by: Chris Evich <[email protected]>
Mainly this is to confirm some changes needed for the podman-py CI setup don't disrupt operations here. Ref: containers/automation_images#111 Signed-off-by: Chris Evich <[email protected]>
Cirrus CI build successful. Image ID |
DO NOT USE: |
Mainly this is to confirm some changes needed for the podman-py CI setup don't disrupt operations here. Ref: containers/automation_images#111 Note: Glibc resolver configuration has changed from previous images. An additional setup command was added to remove systemd-resolved from the chain. Signed-off-by: Chris Evich <[email protected]>
Mainly this is to confirm some changes needed for the podman-py CI setup don't disrupt operations here. Ref: containers/automation_images#111 Note: Glibc resolver configuration has changed from previous images. An additional setup command was added to remove systemd-resolved from the chain. Signed-off-by: Chris Evich <[email protected]>
Mainly this is to confirm some changes needed for the podman-py CI setup don't disrupt operations here. Ref: containers/automation_images#111 Also includes a minor steup fix WRT setting up for test-rpm build. Signed-off-by: Chris Evich <[email protected]>
The one-size-fits-all approach is ever increasingly showing gaps and
inefficiencies WRT CI for the
podman-py
repository. Rather thancontinue to increase the bloat of the golang-centric images, produce a
dedicated image for this repo. This allows pre-installing/caching all
the necessary python bits needed, avoiding the need to install them at
runtime. It will require updates to the
podman-py
setup in order tomake use of the new image effectively.