summaryrefslogtreecommitdiff
path: root/test/checkseccomp/checkseccomp.go
diff options
context:
space:
mode:
authorEd Santiago <santiago@redhat.com>2021-02-09 14:33:19 -0700
committerEd Santiago <santiago@redhat.com>2021-03-21 06:59:01 -0600
commit3baa9da4edec72a70aec4aa25a29b4afd82ed689 (patch)
tree8b7c1c6259c4f041518e7fce271b46dd21639fb5 /test/checkseccomp/checkseccomp.go
parentebc9871c9358b41daefc37e5db8119f596770cb7 (diff)
downloadpodman-3baa9da4edec72a70aec4aa25a29b4afd82ed689.tar.gz
podman-3baa9da4edec72a70aec4aa25a29b4afd82ed689.tar.bz2
podman-3baa9da4edec72a70aec4aa25a29b4afd82ed689.zip
WIP: run buildah bud tests using podman
Set of scripts to run buildah's bud.bats test using podman build in podman CI. podman build is not 100% compatible with buildah bud. In particular: * podman defaults to --layers=true; buildah to false * podman defaults to --force-rm=true; buildah to false * podman error exit status is 125; buildah is 2 * differences in error messages, command-line arguments Some of the above can be dealt with programmatically, by tweaking the buildah helpers.bash (BATS helpers). Some need to be tweaked by patching bud.bats itself. This PR includes a patch that will, I fear, need to be periodically maintained over time. There will likely be failures when vendoring in a new buildah, possibly because new tests were added for new features that don't exist in podman, possibly (I hope unlikely) if existing tests are changed in ways that make the patch file fail to apply. I've tried to write good instructions and to write the run script in such a way that it will offer helpful hints on failure. My instructions and code will be imperfect; I hope they will be good enough to merit continued use of this test (possibly with improvements to the instructions as we learn more about real-world failures). Signed-off-by: Ed Santiago <santiago@redhat.com>
Diffstat (limited to 'test/checkseccomp/checkseccomp.go')
0 files changed, 0 insertions, 0 deletions