[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]

Re: [atomic-devel] moby-engine for centos/epel



I'm not suggesting moby-engine as an alternative to podman, but as an alternative to +1.5 year old docker package


Why? because in OpenSooq.com (where I work) we have mixed environment (centos and fedora),
and since fedora switched from docker to moby-engine I expect centos to follow


> Was there a specific use case that Podman was not meeting?

my concern is that centos version of podman is too old (0.12, latest is 1.12)
and setup of user containers seems not supported (as opposed to fedora), for example

$ podman ps
ERRO[0000] cannot find newuidmap: exec: "newuidmap": executable file not found in $PATH
# yum provides '*/newuidmap'
No matches found

I've already make podman-compose (to replace docker-compose).
But I have two docker-specific projects
one of them give our developers shell access to the container or its logs (using nothing but good old ssh)


and of course this can be ported to podman easily, or even better with podman users can run containers as their own users (but in that case centos needs more recent podman stack too)

the other project listen on docker socket for events and triggers custom shell scripts or python classes or even update haproxy config from a template by reading labels

something like

docker run -d --name wp1 -l glue_http_80_host='wp1.example.com' mywordpress/wordpress

would be added automatically to nginx or haproxy rules using templates


this can also be ported to podman as of v1.2.0 which introduced "podman events",
but the haproxy case is still tricky because there is no way to listen to events on multiple users (can be solved using systemd @ magic, let's say podman-glue myuser)

but non of those are blocker for the adoption of podman,
because we use containers on dev machines
and we don't rely on the above projects

> Is there some particular reason why you still want/need the Moby Engine package?

no, I just want to have that option (even if in a non default repo) for convenient and easy migration and switch between old scripts/ansible playbooks, new fedora ...etc..



On Sun, May 5, 2019 at 10:38 PM Scott McCarty <smccarty redhat com> wrote:
Muayyad,
        Was there a specific use case that Podman was not meeting? Is there some particular reason why you still want/need the Moby Engine package?

Best Regards
Scott M

On Sun, May 5, 2019 at 8:30 AM Muayyad AlSadi <alsadi gmail com> wrote:
> BTW Have you tried out Podman

of course, Podman is an awesome peice of software
BTW: I'm the author of podman-compose and I'm writing an article about buildah for fedora magazine

> I think this is up to a volunteer to take it on.

centos ships too old docker I'm not sure about compatibility 
maybe we should ship moby-engine in a different repo just like we used to do with docker and docker-latest




On Sun, May 5, 2019 at 2:34 PM Daniel Walsh <dwalsh redhat com> wrote:
On 5/5/19 4:33 AM, Muayyad AlSadi wrote:
> Hi,
>
> it seems that fedora had shipped moby-engine,
> when can we ship it for centos/epel?
>
> if not in epel,link for that repo?

I think this is up to a volunteer to take it on.


BTW Have you tried out Podman



--
-- 
Scott McCarty, RHCA
Product Management - Containers, Red Hat Enterprise Linux & OpenShift
Email: smccarty redhat com
Phone: 312-660-3535
Cell: 330-807-1043
Web: http://crunchtools.com

Do Linux Distributions Still Matter with Containers? https://red.ht/2FgQTqq

[Date Prev][Date Next]   [Thread Prev][Thread Next]   [Thread Index] [Date Index] [Author Index]