action #154930
closed
Expand buildah test to Docker
Added by rbranco 5 months ago.
Updated 4 months ago.
Description
Background¶
A recent regression from an API incompatibility between docker and buildah/skopeo in https://bugzilla.suse.com/show_bug.cgi?id=1219563 shows us that we don't test buildah with docker.
We should check if we can extend our buildah test to use docker. This also motivates to separate the buildah part to be an independent test module, which can be run for podman and for docker independently.
Acceptance criterium¶
- Expand
buildah test to use docker
- Refactor the
buildah part to be a separate test module
- Factory first principle applies
References¶
- Description updated (diff)
- Priority changed from Normal to Low
I would put the priority to Normal or even High considering that we're going to ship Docker 25 in the near future.
I'm still reading about buildah and thinking about how to approach this ticket
From https://bugzilla.suse.com/show_bug.cgi?id=1219563#c2 this command should not fail:
buildah from docker-daemon:registry.suse.com/bci/bci-base:15.5
So I guess adding a test for this bug would be as easy as just adding an assert_script_run for that command.
To make it run with docker just add the loadtest 'containers/buildah' ... line in load_host_tests_podman() to load_host_tests_docker().
No additional refactoring needed because buildah is already its own module.
- Status changed from Workable to In Progress
- Status changed from In Progress to Resolved
- % Done changed from 0 to 100
- Status changed from Resolved to In Progress
- Assignee changed from pherranz to ph03nix
- Priority changed from Low to Normal
- Status changed from In Progress to Resolved
Also available in: Atom
PDF