-
Notifications
You must be signed in to change notification settings - Fork 21
Conversation
There is an existing BZ or two about network access when using I could add a separate tag that we could filter on or just wait until the BZs are fixed to merge this. |
I'm okay with waiting for the BZs. Can you copy the BZs here so when they're fixed, I can just re-run and merge this? |
@mike-nguyen my understanding is that we need this containernetworking/plugins#75 merged and then we need a new build of |
Is this temporarily fixed with this: containers/podman#1431 ? |
It should be; but we still have to wait for builds to land across all the platforms. |
bot, retest this please |
This introduces a new role named `podman_pull_run_remove` which is a implementation of `docker_pull_run_remove` using `podman`. The role has been enhanced to test basic running of containers and also testing network access from the container. (These enhancements should likely be applied to `docker_pull_run_remove`, too).
Let's start testing `podman` on the hosts that support it.
5b7b881
to
a1fbd00
Compare
bot, retest this please |
CentOS is still going to fail because the build of |
@miabbott I'm not too concerned about CentOS7. CAHC seems to be failing pulling from registry.access.redhat.com because it doesn't have a cert. If one is required can we put one in or just skip the r.a.rh.com test completely? |
Yeah, the root cause is here: CentOS/sig-atomic-buildscripts#329 I think there is still value in pulling from |
CentOS AH is missing the Red Hat CA cert, so it is unable to pull images from the registry (see: CentOS/sig-atomic-buildscripts#329). To workaround this, we'll have to build the list of images to pull differently for CentOS vs. the rest.
0771e51
to
09c1e56
Compare
Just pushed a new commit with fixes. ⬆️ The CI checks are probably going to fail because OpenStack is bad and should feel bad. |
Look, it worked! |
LGTM! |
podman
is included in most (all?) of the AH streams that we are testing, so let's start making sure it works on Atomic Host.This is a re-implementation of the
docker_pull_run_remove
role that usespodman
. It's slightly more comprehensive than the original role, but still very bare bones.Closes #378