try to build & run on podman via one more hack to resolv.conf parsing

- why the hell does nginx need a resolver config, again?

Author: rpardini

Dockerfile

@@ -1,7 +1,7 @@
 # We start from my nginx fork which includes the proxy-connect module from tEngine
 # Source is available at https://github.com/rpardini/nginx-proxy-connect-stable-alpine
 # This is already multi-arch!
-ARG BASE_IMAGE="rpardini/nginx-proxy-connect-stable-alpine:nginx-1.18.0-alpine-3.12.1"
+ARG BASE_IMAGE="docker.io/rpardini/nginx-proxy-connect-stable-alpine:nginx-1.18.0-alpine-3.12.1"
 # Could be "-debug"
 ARG BASE_IMAGE_SUFFIX=""
 FROM ${BASE_IMAGE}${BASE_IMAGE_SUFFIX}

entrypoint.sh

@@ -1,10 +1,20 @@
 #! /bin/bash
 
+echo "Entrypoint starting."
+
 set -Eeuo pipefail
 trap "echo TRAPed signal" HUP INT QUIT TERM
 
-#configure nginx DNS settings to match host, why must we do that nginx?
-export RESOLVERS=$(awk '$1 == "nameserver" {print ($2 ~ ":")? "["$2"]": $2}' ORS=' ' /etc/resolv.conf | sed 's/ *$//g')
+# configure nginx DNS settings to match host, why must we do that nginx?
+# this leads to a world of problems. ipv6 format being different, etc.
+# below is a collection of hacks contributed over the years.
+
+echo "-- resolv.conf:"
+cat /etc/resolv.conf
+echo "-- end resolv"
+
+# Podman adds a "%3" to the end of the last resolver? I don't get it. Strip it out.
+export RESOLVERS=$(cat /etc/resolv.conf | sed -e 's/%3//g' | awk '$1 == "nameserver" {print ($2 ~ ":")? "["$2"]": $2}' ORS=' ' | sed 's/ *$//g')
 if [ "x$RESOLVERS" = "x" ]; then
     echo "Warning: unable to determine DNS resolvers for nginx" >&2
     exit 66