Open agdevsu opened 2 years ago
i notice that your distro is RHEL. Can you please take this to bugzilla?
Based on the description of @agdevsu I seem to have a similar problem on openSuse MicroOS. I have two pods and the resolution works sometimes on my website and sometimes on my ticketing system, never on both - sometimes osticket.dns.osticket works and sometimes joomla.dns.podman works (logs from nginx podman):
2023/01/23 17:57:59 [emerg] 1#1: host not found in upstream "joomla.dns.podman" in /etc/nginx/conf.d/example.com.conf:27
nginx: [emerg] host not found in upstream "joomla.dns.podman" in /etc/nginx/conf.d/example.com.conf:27
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf is not a file or does not exist
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2023/01/23 17:58:01 [emerg] 1#1: host not found in upstream "osticket.dns.osticket" in /etc/nginx/conf.d/support.example.com.conf:22
nginx: [emerg] host not found in upstream "osticket.dns.osticket" in /etc/nginx/conf.d/support.example.com.conf:22
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf is not a file or does not exist
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2023/01/23 17:58:04 [emerg] 1#1: host not found in upstream "joomla.dns.podman" in /etc/nginx/conf.d/example.com.conf:27
nginx: [emerg] host not found in upstream "joomla.dns.podman" in /etc/nginx/conf.d/example.com.conf:27
/docker-entrypoint.sh: /docker-entrypoint.d/ is not empty, will attempt to perform configuration
/docker-entrypoint.sh: Looking for shell scripts in /docker-entrypoint.d/
/docker-entrypoint.sh: Launching /docker-entrypoint.d/10-listen-on-ipv6-by-default.sh
10-listen-on-ipv6-by-default.sh: info: /etc/nginx/conf.d/default.conf is not a file or does not exist
/docker-entrypoint.sh: Launching /docker-entrypoint.d/20-envsubst-on-templates.sh
/docker-entrypoint.sh: Launching /docker-entrypoint.d/30-tune-worker-processes.sh
/docker-entrypoint.sh: Configuration complete; ready for start up
2023/01/23 17:58:07 [emerg] 1#1: host not found in upstream "osticket.dns.osticket" in /etc/nginx/conf.d/support.example.com.conf:22
nginx: [emerg] host not found in upstream "osticket.dns.osticket" in /etc/nginx/conf.d/support.example.com.conf:22
I'd be really glad if someone could nudge me in the right direction, because I've got no clue where the issue could lie.
podman info:
host:
arch: amd64
buildahVersion: 1.28.0
cgroupControllers:
- cpu
- memory
- pids
cgroupManager: systemd
cgroupVersion: v2
conmon:
package: conmon-2.1.5-2.1.x86_64
path: /usr/bin/conmon
version: 'conmon version 2.1.5, commit: unknown'
cpuUtilization:
idlePercent: 95.71
systemPercent: 2.42
userPercent: 1.87
cpus: 2
distribution:
distribution: '"opensuse-microos"'
version: "20230119"
eventLogger: journald
hostname: pvsr-laweb08
idMappings:
gidmap:
- container_id: 0
host_id: 1001
size: 1
- container_id: 1
host_id: 100000
size: 65536
uidmap:
- container_id: 0
host_id: 1000
size: 1
- container_id: 1
host_id: 100000
size: 65536
kernel: 6.1.7-1-default
linkmode: dynamic
logDriver: journald
memFree: 2121355264
memTotal: 4113506304
networkBackend: cni
ociRuntime:
name: runc
package: runc-1.1.4-2.1.x86_64
path: /usr/bin/runc
version: |-
runc version 1.1.4
commit: v1.1.4-0-ga916309fff0f
spec: 1.0.2-dev
go: go1.18.6
libseccomp: 2.5.4
os: linux
remoteSocket:
exists: true
path: /run/user/1000/podman/podman.sock
security:
apparmorEnabled: false
capabilities: CAP_CHOWN,CAP_DAC_OVERRIDE,CAP_FOWNER,CAP_FSETID,CAP_KILL,CAP_NET_BIND_SERVICE,CAP_SETFCAP,CAP_SETGID,CAP_SETPCAP,CAP_SETUID,CAP_SYS_CHROOT
rootless: true
seccompEnabled: true
seccompProfilePath: /etc/containers/seccomp.json
selinuxEnabled: true
serviceIsRemote: false
slirp4netns:
executable: /usr/bin/slirp4netns
package: slirp4netns-1.2.0-1.1.x86_64
version: |-
slirp4netns version 1.2.0
commit: unknown
libslirp: 4.7.0
SLIRP_CONFIG_VERSION_MAX: 5
libseccomp: 2.5.4
swapFree: 0
swapTotal: 0
uptime: 0h 17m 32.00s
plugins:
authorization: null
log:
- k8s-file
- none
- passthrough
- journald
network:
- bridge
- macvlan
- ipvlan
volume:
- local
registries:
search:
- registry.opensuse.org
- docker.io
store:
configFile: /home/admin/.config/containers/storage.conf
containerStore:
number: 7
paused: 0
running: 6
stopped: 1
graphDriverName: btrfs
graphOptions: {}
graphRoot: /home/admin/.local/share/containers/storage
graphRootAllocated: 21450698752
graphRootUsed: 12955815936
graphStatus:
Build Version: Btrfs v6.1.2
Library Version: "102"
imageCopyTmpDir: /var/tmp
imageStore:
number: 13
runRoot: /run/user/1000/containers
volumePath: /home/admin/.local/share/containers/storage/volumes
version:
APIVersion: 4.3.1
Built: 1673913600
BuiltTime: Tue Jan 17 01:00:00 2023
GitCommit: ""
GoVersion: go1.17.13
Os: linux
OsArch: linux/amd64
Version: 4.3.1
Greetings,
I'm using Podman for containers and the dnsname plugin in order to my Nginx proxy container can resolve the containers name and send requests to the appropriate container. However, sometimes those containers loose their resolution, so the Nginx can't resolve the name and send the request.
Logs generated by Nginx looks like this:
Now,
/run/containers/cni/dnsname/repuestos_default/addhosts
file looks like this:I don't know why this happens. If I reboot the server, the resolution works again.
Output from
podman info
:Thanks for help!