Cannot connect from container to a container #22600
Labels
kind/bug
Categorizes issue or PR as related to a bug.
locked - please file new issue/PR
Assist humans wanting to comment on an old issue or PR with locked comments.
Issue Description
I have ported a project that uses some containers from docker to podman, and they were running successfully with docker. The problem I am encountering is: I have a nginx container that provides access to a container behind it, keycloak. Nginx claims the "keycloak" service name cannot be resolved, but if I get to the nginx container and I nslookup for keycloak, it gets resolved successfully. So... I do not understand what is going on. Is this a know issue of podman, or a problem with the interaction with nginx?
podman version
Client: Podman Engine
Version: 5.0.2
API Version: 5.0.2
Go Version: go1.22.2
Git Commit: 3304dd9-dirty
Built: Thu Apr 18 13:13:19 2024
OS/Arch: linux/amd64
Steps to reproduce the issue
Steps to reproduce the issue
systemctl --user start podman
docker-compose up -d
Describe the results you received
Nginx service fails with
[error] 16#16: *86 keycloak could not be resolved (110: Operation timed out), client: 10.89.1.4, server: keycloak.local, request: "GET / HTTP/1.1", host: "keycloak.local:8443"
. However, should I executedocker-compose exec -it nginx wget http://keycloak:8080 -O -
I get the expected output, and I executedocker-compose exec -it nginx nslookup keycloak
I get backDescribe the results you expected
nginx can connect to keycloak, as was happening with docker.
podman info output
Podman in a container
No
Privileged Or Rootless
Rootless
Upstream Latest Release
Yes
Additional environment details
I am running on arch linux.
Additional information
Additional information like issue happens only occasionally or issue happens with a particular architecture or on a particular setting
The text was updated successfully, but these errors were encountered: