podman-compose up run failure！I need some help!

[JohyC]

Describe the bug
A clear and concise description of what the bug is.

Please make sure it's not a bug in podman (in that case report it to podman)
or your understanding of docker-compose or how rootless containers work (for example, it's normal for rootless container not to be able to listen for port less than 1024 like 80)

please try to reproduce the bug in latest devel branch

To Reproduce
Steps to reproduce the behavior:

1. what is the content of the current working directory (ex. docker-compose.yml, .env, Dockerfile, ...etc.)

I used https://github.com/containers/podman-compose/blob/devel/examples/busybox/docker-compose.yaml

2. what is the sequence of commands you typed

Just use podman-compose up

please use minimal reproducible example for example give me a small busybox-based compose yaml

Expected behavior
A clear and concise description of what you expected to happen.

Actual behavior
What is the behavior you actually got and that should not happen.

Output

$ podman-compose --version

['podman', '--version', '']
using podman version: 3.0.1
podman-composer version  1.0.3
podman --version
podman version 3.0.1
exit code: 0

$ podman-compose up

error.txt

**Environment:**
 - OS: Linux 5.10.28-aml-s812 armv7l 
 - podman version: 3.0.1
 - podman compose version: (git hex) 1.0.3

**Additional context**

![image](https://user-images.githubusercontent.com/38210128/148389566-366fa0ea-110c-4e79-8ab1-6edf4ce5c66f.png)

[muayyad-alsadi]

Error: unrecognized command `podman network exists`

from the readme

If you have legacy version of podman (before 3.1.0) you might need to stick with legacy podman-compose 0.1.x branch. The legacy branch 0.1.x uses mappings and workarounds to compensate for rootless limitations.

Modern podman versions (>=3.4) do not have those limitations and thus you can use latest and stable 1.x branch.

either upgrade to podman >= 3.1.0
or use 0.1.x branch of podman-compose

[JohyC]

Error: unrecognized command `podman network exists`

from the readme

If you have legacy version of podman (before 3.1.0) you might need to stick with legacy podman-compose 0.1.x branch. The legacy branch 0.1.x uses mappings and workarounds to compensate for rootless limitations.

Modern podman versions (>=3.4) do not have those limitations and thus you can use latest and stable 1.x branch.

either upgrade to podman >= 3.1.0 or use 0.1.x branch of podman-compose

Ok! I got it.thanks man!