miabbott added a new comment to an issue you are following: ``
Assuming
podman doesn't break existing Docker workflows it doesn't pull in buildah as a dep
``` # rpm-ostree install podman Checking out tree ba63713... done Enabled rpm-md repositories: updates-testing updates fedora rpm-md repo 'updates-testing' (cached); generated: 2018-04-10 22:36:28 rpm-md repo 'updates' (cached); generated: 2018-02-20 19:18:14 rpm-md repo 'fedora' (cached); generated: 2018-04-10 21:11:42
Importing metadata [=============] 100% Resolving dependencies... done Will download: 3 packages (19.8 MB)
Downloading from updates-testing: [=============] 100%
Importing (3/3) [=============] 100% Applying 4 overlays
Building filesystem (4/4) [=============] 100% Running pre scripts... 0 done Running post scripts... 7 done Writing rpmdb... done Writing OSTree commit... done Copying /etc changes: 20 modified, 0 removed, 57 added Transaction complete; bootconfig swap: no deployment count change: 0 Added: buildah-0.16-1.git82529cd.fc28.x86_64 containernetworking-cni-0.6.0-4.fc28.x86_64 podman-0.4.1-1.gitb51d327.fc28.x86_64 Run "systemctl reboot" to start a reboot ```
Well, `buildah` does get dragged in. The on disk size of the `buildah` binary is 12M.
In [406](https://pagure.io/atomic-wg/issue/406) we settled on using a `buildah` container image, just 2 months ago, but that doesn't mean we can't change our minds.
I'm +1 for including both `podman` and `buildah` if we have to. ``
To reply, visit the link below or just reply to this email https://pagure.io/atomic-wg/issue/422