Describe the bug
I have a podman-compose.yaml (derived from docker-compose.yaml which we have had been and working well for us).
If has multiple services and some of them with multiple instances replicas with cpu and memory limits. Also these services talk on a common network (using names/aliases).
I am facing this problem that first with getting this up on a non-root user with errors related to cgroup and then I moved to root user and there facing challenges on making the services talk using names. Are these problems still there with latest podman and podman-compose or is there a way to work around these ?
Describe the bug I have a podman-compose.yaml (derived from docker-compose.yaml which we have had been and working well for us). If has multiple services and some of them with multiple instances replicas with cpu and memory limits. Also these services talk on a common network (using names/aliases).
I am facing this problem that first with getting this up on a non-root user with errors related to cgroup and then I moved to root user and there facing challenges on making the services talk using names. Are these problems still there with latest podman and podman-compose or is there a way to work around these ?