Can't connect to podlet-generated pod containers for quadlet, yet regular compose-ed pod is working fine

[tiritto]

I have a podman-compose.yaml file that creates a fully functional pod when I do podman-compose up. I can connect to it from the browser just as expected and everything works fine. However, I wanted to turn it into a quadlet, so to achieve this purpose, I've used podlet -u compose --pod podman-compose.yaml. It created the files and I could start my pod using systemctl --user, but for some reason I am unable to connect to any container inside this pod. The same configuration works just right away with compose.

I've seen the issue #90 and manually added .network to my .container files, but it still doesn't resolve the issue.

I tried to connect to it using both localhost:port (this work when run from compose) and containerName:port, but I couldn't connect to it in either case. Using curl gives me (56) Recv failure and (6) Could not resolve host respectively.

journalctl doesn't report any issues for systemctl --user daemon-reload nor systemctl --user start sonarr-pod /usr/lib/systemd/system-generators/podman-system-generator --user --dryrun doesn't report any issues as well. I can also confirm that each individual container in itself is also running just fine.

Am I doing something wrong or missing something crucial here?

The content of my podman-compose.yaml is as follows:

---
name: sonarr
services:
  sonarr:
    image: lscr.io/linuxserver/sonarr:latest
    container_name: sonarr
    networks:
      - media_network
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Warsaw
    volumes:
      - sonarr_config:/config
      - /media/MediaStorage:/data/media
      - /home/tiritto/Pobrane/Torrenty:/downloads
    ports:
      - 8989:8989
    restart: unless-stopped

  qbittorrent:
    image: lscr.io/linuxserver/qbittorrent:latest
    container_name: qbittorrent
    networks:
      - media_network
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Europe/Warsaw
      - WEBUI_PORT=8080
      - TORRENTING_PORT=6881
    volumes:
      - qbittorrent_config:/config
      - /home/tiritto/Pobrane/Torrenty:/downloads
    ports:
      - 8080:8080
      - 6881:6881
      - 6881:6881/udp
    restart: unless-stopped

networks:
  media_network:

volumes:
  sonarr_config:
  qbittorrent_config:

podman version 5.1.1 podlet 0.3.0 Nobara Linux 40 (based on Fedora 40)

[analisis1data]

I'm having the same issue right now.

I created a pod from a Kubernetes YAML file generated from a Docker Compose file, and it works fine. However, I don’t achieve the same result when using compose --pod and systemd --user. The network is created as specified, but when I attempt to access a service via the Firefox web browser, it shows a “PR_END_OF_FILE_ERROR.” Interestingly, it doesn’t require the corresponding service’s container to be up; it only needs the pod to be running.

Fedora CoreOS 40.20240602.3.0 Podman 5.0.3 Podlet 0.3.0