$ podman inspect: limits, networks, published ports
messenger-lab3_api_1 cpus=1000000000 memory=268435456 networks=messenger-lab3_backend messenger-lab3_edge ports=
messenger-lab3_api_2 cpus=1000000000 memory=268435456 networks=messenger-lab3_backend messenger-lab3_edge ports=
messenger-lab3_lb_1 cpus=500000000 memory=67108864 networks=messenger-lab3_edge ports=8080/tcp->0.0.0.0:8080 
messenger-lab3_migrate_1 cpus=500000000 memory=67108864 networks=messenger-lab3_backend ports=
messenger-lab3_postgres_1 cpus=1000000000 memory=536870912 networks=messenger-lab3_backend ports=5432/tcp->127.0.0.1:55432 
messenger-lab3_redis_1 cpus=500000000 memory=134217728 networks=messenger-lab3_backend ports=6379/tcp->127.0.0.1:56379 

$ ls /run/secrets in each running container
messenger-lab3_api_1: cache_url database_url 
messenger-lab3_api_2: cache_url database_url 
messenger-lab3_lb_1: 
messenger-lab3_postgres_1: postgres_password 
messenger-lab3_redis_1: 
migrate (one-shot): /run/secrets/database_url 

$ lb sees only the edge network
postgres: not resolvable from lb
redis: not resolvable from lb
10.89.4.28        api.dns.podman  api.dns.podman api

$ grep -c container_name compose.yaml
0
