Muayyad Alsadi

We had to log too much things because this project was in early stages and they help us debug The project is now stable and we should make it default...

does merging the colored logs solve this?

you can pass `podman-compose --podman-args ...` or `podman-compose --podman-run-args ...` or `podman-compose --podman--start-args ...` I liked the idea of `x-podman` in yaml.

Regarding volumes, just like docker-compose you must pass `-v`

most likely this is the change you are talking about > The --net=container: option to podman run, podman create, and podman pod create now conflicts with the --add-host option.

I'm using podman 4.1 and I have no issue I've just tested [nets_test2 stack](https://github.com/containers/podman-compose/blob/devel/tests/nets_test2/docker-compose.yml) with the latest devel branch ``` $ rpm -q podman podman-4.1.1-3.fc36.x86_64 $ podman-compose up -d $...

why is this closed? this is a very valid point. I'll reopen it

I've activated pytests on `pytests/*.py` Those are intended to be unit tests of python methods (no actual creation of containers) I want to add more tests that involves actually launching...

the term pod means containers that shares volumes and network namespaces (think of it as a host) if you put multiple containers on one single pod, sharing network means you...

can we ask podman to prefix output lines with custom string just like ``` podman start -a web | sed -re 's#^#WEB: #' ```