Closed bukovszg closed 1 year ago
I figured out at least one part of the problem. The DNS issues were coming from a /etc/resolv.conf setting of the host itself:
# Any changes made to this file will be lost
# The default domain name if none is supplied
search internal.domain other.domain
# The list of name servers
nameserver X.Y.Z.W
nameserver A.B.C.D
# The list of options
options timeout:2
options attempts:3
options rotate
This gets copied into the container by podman - it the extends it with settings for the podman internal name resolution:
search dns.podman internal.domain other.domain
nameserver 192.168.2.1
nameserver X.Y.Z.W
nameserver A.B.C.D
options attempts:3
options rotate
due to option rotate however, all DNS queries are rotated, sometimes hitting the podman-internal DNS sometimes hitting the external DNS. The external DNS obviously knows nothing about the podman internal DNS names, causing random DNS resolution errors.
Don't think this is an issue with the image itself. Consider opening an issue at https://github.com/containers/podman-compose
Behaviour
I have encountered several issues when trying to run the container with podman-compose.
Steps to reproduce this issue
Expected behaviour
Container starts, can read/.write all the database tables, dispatcher registers as poller
What has been checked
DNS confirmed working:
DB is reachable and populated:
Configuration
Docker version (type
docker --version
) :podman version 4.1.1
Docker compose version if applicable (type
docker-compose --version
) :Platform (Debian 9, Ubuntu 18.04, ...) :
System info (type
uname -a
) :Linux <REDACTED> 4.18.0-372.26.1.el8_6.x86_64 #1 SMP Sat Aug 27 02:44:20 EDT 2022 x86_64 x86_64 x86_64 GNU/Linux
Include all necessary configuration files :
docker-compose.yml
,.env
, ...Docker info
Logs
compose.txt logsnippets.txt librenms_dev.txt