Patrick

Today tried to use wait4x on my local domains, like https://router.docker, or https://auth.wod.docker And I don't understand, is this problem, because I've installed custom certs with mkcert on my machine,...

Output: **Wait4X with debug** ``` ➜ wait4x http https://router.docker -l debug 2022-11-29T12:43:09+02:00 INF [HTTP] Checking the https://router.docker ... 2022-11-29T12:43:09+02:00 DBG Get "https://router.docker": dial tcp: lookup router.docker on 100.64.0.2:53: no such...

@mortymacs ➜ dig router.docker @100.64.0.2 ; DiG 9.10.6 router.docker @100.64.0.2 ;; global options: +cmd ;; Got answer: ;; ->>HEADER

I'm using [dnsmasq](https://thekelleys.org.uk/dnsmasq/doc.html) on my mac, and my ansible role https://github.com/wayofdev/ansible-role-dnsmasq to setup dns on mac machines. ➜ cat /etc/resolver/docker nameserver 127.0.0.1 ➜ pwd /opt/homebrew/etc ➜ cat dnsmasq.conf address=/docker/127.0.0.1 address=/mac/127.0.0.1

@mortymacs tried locally using binary and through docker (in separate image) ➜ which wait4x /usr/local/bin/wait4x Quick result, using docker image: ``` docker run --rm --name='wait4x' \ atkrad/wait4x:latest http https://router.docker -l...

Temporary, working solution **docker-compose.yaml:** ``` ... keycloak: image: quay.io/keycloak/keycloak:20.0.1 container_name: ${COMPOSE_PROJECT_NAME_SAFE}_keycloak restart: on-failure ports: - "8765:8080" ... ``` **Makefile:** ``` _kc-wait: $(DOCKER) run --rm --net=host --name='wait4x' atkrad/wait4x:latest \ http $(shell...