The upstream libpod project (https://github.com/projectatomic/libpod/) would love to have an AH F27 variant without docker and with podman and its friends. This would be only used in our PAPR CI tests and perhaps for debug. We understand a more official project is in the works for this and is being tracked by issue #422.
Today we currently use an F27 cloud image and install the packages we need. We would prefer that this be done predeployment and use AH instead of cloud.
IMO, it seems unlikely that the WG will commit to delivering a custom spin of F27AH with these changes.
However, it would be pretty straight forward for someone to create a custom compose with the changes you asked for. I'm thinking some sort of Jenkins job in either CentOS CI or the internal RH Jenkins instance that could handle it.
You might want to file an issue over at PAPR for this.
especially considering #422 (i.e. we want podman to work well with atomic host and may even include it in the base image in the future) then it's probably a good idea to help brent and team get this set up. @miabbott I agree something official is probably hard to do (i don't think they really need anything official) and that setting up a centos CI job for this would be ideal.
@smilner let's consider this and see if we can have someone help brent and team set it up.
We'll use this as a tracking bug.
yeah, this is def not an official image. it would only be for podman CI tests and debug and should give you guys a good idea for #422 in the end.
Metadata Update from @dustymabe: - Issue tagged with: host, jira, question
My vote is that we instead change the podman CI to do something similar to https://github.com/ostreedev/ostree/pull/1462
That approach lets you easily customize the VM in whatever way you want beforehand.
If this is just for CI purposes, you should be able to do what you need directly from PAPR. For example, you can systemctl mask --now docker.service and overlaying podman using the same DESTDIR= tricks as in e.g. projectatomic/atomic.
systemctl mask --now docker.service
DESTDIR=
Yeah I was simply hoping for predeployment customization.
Is this still needed or is papr working for this?
Right now, we customize and reboot for our Fedora Atomic Host tests
@baude I guess what I'm asking is do we need to make any changes for you to continue running with this or is the current functionality workable?
podman is in atomic host now. pretty sure we are good here.
Metadata Update from @dustymabe: - Issue close_status updated to: Fixed - Issue status updated to: Closed (was: Open)
Login to comment on this ticket.