error adding pod to state: name root is in use: pod already exists

[peterwillcn]

error adding pod to state: name root is in use: pod already exists

version: "2"

services:
s1:
hostname: s1
.....
s2:
hostname: s2
.....

# podman-compose -f /root/1234.yml up -d
podman pod create --name=root --share net -p 1234:4321/udp -p 1234:4321/tcp
podman run --name=root_s1_1 -d --pod=root --label io.podman.compose.config-hash=123 --label io.podman.compose.project=root --label io.podman.compose.version=0.0.1 --label com.docker.compose.container-number=1 --label com.docker.compose.service=s1 ..... --hostname s1 

# podman-compose -f /root/2345.yml up -d
podman pod create --name=root --share net -p 2345:4321/udp -p 2345:4321/tcp
error adding pod to state: name root is in use: pod already exists
125
podman run --name=root_s2_1 -d --pod=root --label io.podman.compose.config-hash=123 --label io.podman.compose.project=root --label io.podman.compose.version=0.0.1 --label com.docker.compose.container-number=1 --label com.docker.compose.service=s2 ..... --hostname s2
```

[runephilosof-abtion]

You have to run podman-compose down between up.
It is annoying and not the same behavior as docker-compose.

[alec-w]

Is there anything that can be done about this?

Since we don't have health checks yet either (see #866, #23 and #921) I was going to work around that by running

podman compose up -d service1

while [ "$(podman compose ps -f json | jq '.[] | select(.Labels."com.docker.compose.service"=="service1").Status | contains("healthy")')" == "false" ]; do
    :
done

podman compose up -d service2

However, this issue prevents that as well. Seems the only options would be to have 2 separate compose files and use the script workaround or drop podman-compose and switch to docker-compose instead (which I'd been hoping to avoid).