4:42 a.m.
Hi Jerome,
I went with the manual approach of creating a pod, creating two containers in it and then
starting the pod. First, I had tried to export my local setup (created as mentioned above)
to a yaml file and then play it on my server, but sadly podman-exported yaml files are not
100% portable, especially when there are host bind-mounted volumes. I'm not sure this
is a limitation of Podman or something else, but it would be cool if the file only used
`pwd` equivalents instead of inserting constant paths to volume definitions.
Nevertheless, Podman Compose seems interesting and powerful.
Thanks for your suggestion
-Mehdi
On Wednesday, June 5, 2024 at 10:45:37 AM GMT+3:30, Jérôme Radix
<jerome.radix(a)gmail.com> wrote:
Hello,
You have podman-compose for that.
https://github.com/containers/podman-compose
Regards
Jérôme.
Le mar. 4 juin 2024 à 13:50, Mehdi Haghgoo via Podman <podman(a)lists.podman.io> a
écrit :
I have problem running docker-compose on a Rocky Linux server 9.4.
Instead of Docker Compose, I want to use Podman. A service in my compose.yaml file creates
a container on the fly using Containerfile and runs the service.
When running an container equivalent to this service, how can I create the container on
the fly by first building using the Containerfile and then bringing up the service?
Is this possible?
Or should I first create a custom image, push it to repo and pull it before running the
container?
_______________________________________________
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