Connect 2 containers rootless with postman-compose?

Hello,

I have two Podman containers. One container that contains Linkstack and another container for the Nginx Proxy Manager. Now I want the Nginx Proxy Manager to retrieve the website from the Linkstack container. Unfortunately this does not work.

I integrate the two containers in a network. I realize this with podman-compose.

First, I created the network with "podman network create n_webservice".

Compose.yaml

services: NGINXPM: networks: - n_webservice container_name: NGINXPM volumes: - /home/fan/pod_volume/npm/data/:/data/ - /home/fan/pod_volume/npm/letsencrypt/:/etc/letsencrypt ports: - 8080:80 - 4433:443 - 9446:81 image: docker.io/jc21/nginx-proxy-manager:latest linkstack: networks: - n_webservice container_name: linkstack ports: - 4430:80 image: docker.io/linkstackorg/linkstack networks: n_webservice: external: n_webservice

I have tried everything possible in the Nginx Proxy Manager with the entry, but unfortunately I can't get any further. The destinations http://linkstack:4430 and http://127.0.0.1:4430 are not working.

Can someone please help me how I can access the linkstack container from the NGINXPM container?

6 comments

I had the same issues when I first started out with podman. The solution I found was to make a pod and place the containers within the pod. They'll be able to access each other through localhost:port. If you need ports published outside the pod, then they'll need to be specified during pod creation.
I didn't use podman-compose, so I can't speak specifically to how you'll go about this with a compose yaml.
It took many pages of websites for me to find something I understood. I'll see if I can find which websites I used and post them in a bit.
- Thank you 🙏 Can you post a sample for the configuration, please?
  
  Took awhile, but here's how to get the previously mentioned article working at a basic level. I'll write this out for future people in case they come across this post.
  If you would like to reset podman to factory default (i.e. absolutely nothing configured), then you can start with the below command. I used this a lot when testing out different things in podman to help give me a clean slate.
  undefined
  
  podman system reset --force
  Create the pod and containers within the pod. Note the pod is treated like a container itself, so we publish the ports on the pod instead of the containers.
  undefined
  
  podman pod create --restart unless-stopped -p 8080:80 -p 4443:443 -h podhost testpod podman run -dt --pod testpod --name httpd docker.io/jitesoft/lighttpd:latest podman run -dt --pod testpod --name alpine docker.io/library/alpine:latest
  And to test I did:
  undefined
  
  podman exec -it alpine apk update && apk upgrade podman exec -it alpine apk add curl podman exec -it alpine curl http://localhost
  Which will return the default 404 page since lighttpd is not configured.
  And then running curl outside the container on localhost will present with the same default 404 page:
  curl http://localhost:8080
  This may not fit your exact use-case, but with the article it should get you going. If using pods, macvlan, or slirp4netns, you should be headed in the right direction.
  I'll repost the sources that led me down this path here:
  Podman starting tutorial
  https://github.com/containers/podman/blob/main/docs/tutorials/podman_tutorial.md
  Podman network tutorial
  https://github.com/containers/podman/blob/main/docs/tutorials/basic_networking.md
  Redhat Container Networking article
  https://www.redhat.com/sysadmin/container-networking-podman
  Baeldung Communication Between Containers
  https://www.baeldung.com/linux/rootless-podman-communication-containers
  
  Here is the article I used to help me understand what I wanted to do. Hiding away in the actual Podman tutorials lol. Once I get my laptop up and running, i'll post my config since it's running in my learning environment and I haven't done anything with podman in my prod homelab; however, this let me get two containers (database and webapp) connecting together.
  https://github.com/containers/podman/blob/main/docs/tutorials/basic_networking.md#Communicating-between-containers-and-pods
  My environment is podman in AlmaLinux 9.4 SELinux inside a Hyper-V VM on Windows 11. I can access the webpapp in the podman pod from outside my laptop.

6 comments

And then running curl outside the container on localhost will present with the same default 404 page: curl http://localhost:8080

And then running curl outside the container on localhost will present with the same default 404 page:
`curl http://localhost:8080`