Muayyad Alsadi

> I see this as a major problem. it's a standard YAML, we are not reinventing the wheel here. > This porject should inherit AT LEAST the upstream tests, I...

> For instance, even now I can't use object as a port mapping, I've just solved this, you can now use object port mapping. > rather then copying it locally....

> If compose could send over the location of the context directory rather then copying it locally. as far as I know and as far as podman-compose is concern, compose...

## Question? what version of podman-compose are you using? ## NOTE the `external` part in networks mean you need to manage it yourself, you should create this network, see [compose...

would you please try latest branch. ``` pip3 install https://github.com/containers/podman-compose/archive/devel.tar.gz ``` I've tested it with equivalent yaml and it worked ```yaml --- version: "3" networks: podman: ipam: driver: default config:...

> , but is there a command to stop that from happening in the compose file. or just a general way of setting pod configuration? to prevent creating a pod...

Use latest devel branch as in the readme

``` pip3 install https://github.com/containers/podman-compose/archive/devel.tar.gz ``` or ``` pip3 install --user https://github.com/containers/podman-compose/archive/devel.tar.gz ```

@andrew-womeldorf please test. NOTE: it's preferred to use list for command and entrypoint not strings. the compose specs refer to [dockerfile](https://docs.docker.com/engine/reference/builder/#entrypoint) which says: Quote: The exec form, which is the...

Install it like this ``` pip3 install https://github.com/containers/podman-compose/archive/devel.tar.gz ```