containers / containers/podman-compose

podman-compose

Open
#863 0 comments 0 reactions 0 assignees View on GitHub
bug
Dominant language
Python
Stars
6.2k
Forks
622
PR merge metrics
No merged PRs in 30d

Description

**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 ?

Contributor guide

Open the contributing guide

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.