[atomic-wg] Issue #422: Evaluate podman for inclusion in atomic host

[Dusty Mabe]

dustymabe reported a new issue against the project: `atomic-wg` that you are following:
``
We've had a few discussions about including `cri-o` in atomic host and one
[recently](https://pagure.io/atomic-wg/issue/407) discussing both `cri-o` and `podman`.
The consensus on `cri-o` was that if someone needs to get openshift/kubernetes then
it's not that much harder to also get `cri-o` as part of the same process (for
example, using the `openshift-ansible` installer). 

`podman`, however, is something we could consider adding because it gives us a nice
familiar CLI with possibly less bloat. `podman` is brand new and there is still some work
to be done on it. It was decided that we should evaluate adding `podman` into atomic host
in a few months time. This was proposed at the [feb 7th WG
meeting](https://lists.projectatomic.io/projectatomic-archives/atomic-devel/2018-February/msg00024.html).
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Brent Baude]

baude added a new comment to an issue you are following:
``
I would be happy to help with this as well.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Steve Milner]

smilner added a new comment to an issue you are following:
``
Thanks @baude!
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Steve Milner]

smilner added a new comment to an issue you are following:
``
We should bring this up in our next meeting. As to if this should be in the OSTree compose
or if it should be added on someway. From a conversation I just had it was noted that
``podman`` invokes ``buildah`` in some cases.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Ben Breard]

mrguitar added a new comment to an issue you are following:
``
@baude, right now we're on a path to consume buildah via a container on atomic host. I
this having podman in the compose makes sense, but I see some issues with `podman build.
Any thoughts?
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Ben Breard]

mrguitar added a new comment to an issue you are following:
``
oh, what @smilner said. :)
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Brent Baude]

baude added a new comment to an issue you are following:
``
As of now, podman can live without buildah. I believe the build command is not displayed
if no buildah is found.  Though this does complicate things.  Is buildah going to be put
in a container due to size restrictions ?
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Steve Milner]

smilner added a new comment to an issue you are following:
``
Binary/content size is a factor when adding new things to the compose. ``buildah`` was put
into a container just so it wouldn't be yet another thing added to the base while
still allowing people to use it. If we were to move to putting these both into the compose
it would be ideal for them to share any common code via a buildmode of ``plugin`` or
``c-shared`` to keep reused code from increasing the base image size if possible.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Brent Baude]

baude added a new comment to an issue you are following:
``
We are currently working on more code usage between podman, buildah, and crio. 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Steve Milner]

smilner added a new comment to an issue you are following:
``
@baude / @mrguitar: @dustymabe asked in today's meeting if podman was stable enough to
be included as well as if it would interact with docker in any way.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Steve Milner]

smilner added a new comment to an issue you are following:
``
```
12:58:29 dustymabe | another question.. how does it interact with docker if they are both
installed?
12:58:45 dustymabe | I say first step.. add it to rawhide
12:58:53 dustymabe | I'm not opposed to doing that today
12:58:54   jbrooks | layered, rebooted, and "podman run centos echo foo" works
:)
13:00:05   ashcrow | dustymabe: I threw the questions in the issue, but there should be no
side effects with docker
13:00:12   walters | I'm +1 to adding to AH by default
13:00:15    jlebon | how about: ask devs if they think it's ready for wider
consumption, if yes, add to rawhide
13:00:36   ashcrow | That sounds good to me
13:00:40   walters | one of the biggest things you'll note is it doesn't share
image storage with docker
13:00:57   jbrooks | It's in the fedora repos
13:01:04   jbrooks | So it's already considered that stable
13:01:14   jbrooks | easily stable enough to just stick it in rawide
13:01:16   jbrooks | hide
13:01:32     mheon | jbrooks: i feel obligated to note that we are officially alpha, but i
would say we are definitely rawhide level stable
```
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
I think this is something we can put in rawhide today.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Steve Milner]

The issue: `Evaluate podman for inclusion in atomic host` of project: `atomic-wg` has been
assigned to `smilner` by smilner.

https://pagure.io/atomic-wg/issue/422

[Steve Milner]

smilner added a new comment to an issue you are following:
``
I'll look at getting this into rawhide.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Steve Milner]

smilner added a new comment to an issue you are following:
``
https://pagure.io/fedora-atomic/pull-request/117
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Steve Milner]

smilner added a new comment to an issue you are following:
``
The PR has merged and ``podman`` should be added in the next rawhide compose.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Steve Milner]

smilner added a new comment to an issue you are following:
``
@baude noted that he was able to test podman in a rawhide compose and things worked well.
:grinning: 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Dusty Mabe]

dustymabe 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

Should we add podman to Atomic Host for f28? 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Jonathan Lebon]

jlebon added a new comment to an issue you are following:
``
That sounds good to me!
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Jason Brooks]

jasonbrooks 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
>  
>  Should we add podman to Atomic Host for f28?
>  
+1
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Sanja Bonic]

sanja added a new comment to an issue you are following:
``
+1 for adding podman
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Micah Abbott]

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

[Brent Baude]

baude added a new comment to an issue you are following:
``
I am working to sever that dependency.  should know next week if I can make that happen.
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Steve Milner]

smilner added a new comment to an issue you are following:
``
>  In 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. 
>  
I second this
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
right now buildah is also pulled in via deps.

```
[root@vanilla-f28-atomic ~]# dnf install podman | tee
Last metadata expiration check: 0:01:11 ago on Wed 11 Apr 2018 06:56:02 PM UTC.
Dependencies resolved.
================================================================================
 Package                 Arch   Version                   Repository       Size
================================================================================
Installing:
 podman                  x86_64 0.4.1-1.gitb51d327.fc28   updates-testing 5.5 M
Installing dependencies:
 buildah                 x86_64 0.16-1.git82529cd.fc28    updates-testing 3.7 M
 containernetworking-cni x86_64 0.6.0-4.fc28              updates-testing 9.7 M

Transaction Summary
================================================================================
Install  3 Packages

Total download size: 19 M
Installed size: 65 M
Is this ok [y/N]: N
Operation aborted.
```

so download size is 19M and installed size is 65M 
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422

[Dusty Mabe]

The status of the issue: `Evaluate podman for inclusion in atomic host` of project:
`atomic-wg` has been updated to: Closed as Fixed by dustymabe.

https://pagure.io/atomic-wg/issue/422

[Dusty Mabe]

dustymabe added a new comment to an issue you are following:
``
This was added to f28AH: https://pagure.io/fedora-atomic/pull-request/118

Updating this issue to closed
``

To reply, visit the link below or just reply to this email
https://pagure.io/atomic-wg/issue/422