7:41 a.m.
Depending on the complexity of the task, podman generate kube and
podman play kube may also be an answer.
https://developers.redhat.com/blog/2019/01/29/podman-kubernetes-yaml/
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
https://github.com/containers/podman-compose.
Unfortunately, in my case it was not able to replace docker's compose
completely¹.
But podman-compose has a option to trace what it is trying to do.
This
helped me, to write a simple script, which is doing the same job as
the
initial composer file.
Uwe
¹) 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
a
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