The issue with docker-compose is it is huge and we don't have the
engineering staff to work and respond to all requests for support on
compose. Our team is goaled at supporting the traditional container
work loads on a single node. And helping people move to the multi-node
containers via Kubernetes and OpenShift.
We work with the community to support other features like compose and
would not be against adding features provided by the community to better
integrate podman into the compose world, but we don't have the time or
staff to do the work ourselves.
As far as documenting how to move a traditional container workload to
Kubernetes, we would be interested in this.
On 9/2/19 4:09 AM, Uwe Reh wrote:
do you really think, that your article is an appropriate answer to the
initial question? I suppose not.
Surely you've mad a good job for people which are familiar with
Kubernets. For beginners like Robert and me, it's some kind of chinese.
Just try to imaging:
- you are relatively new in the area of containers.
- you have heard just enough about Kubernets, to realize that it's out
of scope for your needs.
- you have read about Kubernet's 'kompose' and have seen your article.
A beginner like me, may think, "Ok, sounds reasonable".
But this leads into an dead end. 'kompose' creates a lot of nice
detailed configuration files, but none of them seems to be suitable for
Without any experience or deeper knowledge about Kubernet, I resigned.
Maybe, you could write a detailed howto for the new podman pages.
Am 30.08.19 um 13:41 schrieb Brent Baude:
> Depending on the complexity of the task, podman generate kube and
> podman play kube may also be an answer.
> While most of the article talks about replaying on a kube-basaed
> runtime, one of the last paragraphs talks about replaying locally.
> On Fri, 2019-08-30 at 13:09 +0200, Uwe Reh wrote:
>> Hi Robert,
>> I'm not an expert at all. But I had this question a few days ago.
>> The most common tool seems to be
>> Unfortunately, in my case it was not able to replace docker's compose
>> But podman-compose has a option to trace what it is trying to do.
>> helped me, to write a simple script, which is doing the same job as
>> initial composer file.
>> ¹) Sorry I haven't documented the problem well.
>> As far as I remember, the problem was that composer creates/runs
>> standalone containers with different IPs and an implicit DNS service
>> (container name -> ip). podman-compose creates a pod, which means all
>> containers in this pod share the IP 'localhost'. Im my case this was
>> problem, because the application on one container was looking for
>> resources on the host 'mysql'.
>> Podman mailing list -- podman(a)lists.podman.io
>> To unsubscribe send an email to podman-leave(a)lists.podman.io
> Podman mailing list -- podman(a)lists.podman.io
> To unsubscribe send an email to podman-leave(a)lists.podman.io
Podman mailing list -- podman(a)lists.podman.io
To unsubscribe send an email to podman-leave(a)lists.podman.io