Closed AlexSkrypnyk closed 8 months ago
Since upgrading to the latest pygmy images a couple of weeks ago, none of the URLs set through the amazeio network cannot resolve DNS.
amazeio
I was able to narrow this down to the following pygmy configuration that allowed me to isolate this particular image:
pygmy
# This config leads to not working. --- services: amazeeio-haproxy: image: pygmystack/haproxy:v0.0.1 amazeeio-ssh-agent: image: pygmystack/ssh-agent:v0.0.1 amazeeio-dnsmasq: image: pygmystack/dnsmasq:v0.1.0 amazeeio-mailhog: image: pygmystack/mailhog:v0.0.1
Looking at the changes between this image versions: https://github.com/pygmystack/dnsmasq/compare/v0.0.1...v0.1.0#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557R3
Looks like dnsmasq-dnssec was updated from 2.85 to 2.90
dnsmasq-dnssec
2.85
2.90
Here is a link to the changelog: https://thekelleys.org.uk/dnsmasq/CHANGELOG
System information report OPERATING SYSTEM ProductName: macOS ProductVersion: 14.4 BuildVersion: 23E214 DOCKER Path to binary: /usr/local/bin/docker Docker version 25.0.3, build 4debf41 Client: Version: 25.0.3 Context: desktop-linux Debug Mode: false Plugins: buildx: Docker Buildx (Docker Inc.) Version: v0.12.1-desktop.4 Path: /Users/o_o/.docker/cli-plugins/docker-buildx compose: Docker Compose (Docker Inc.) Version: v2.24.6-desktop.1 Path: /Users/o_o/.docker/cli-plugins/docker-compose debug: Get a shell into any image or container. (Docker Inc.) Version: 0.0.24 Path: /Users/o_o/.docker/cli-plugins/docker-debug dev: Docker Dev Environments (Docker Inc.) Version: v0.1.0 Path: /Users/o_o/.docker/cli-plugins/docker-dev extension: Manages Docker extensions (Docker Inc.) Version: v0.2.22 Path: /Users/o_o/.docker/cli-plugins/docker-extension feedback: Provide feedback, right in your terminal! (Docker Inc.) Version: v1.0.4 Path: /Users/o_o/.docker/cli-plugins/docker-feedback init: Creates Docker-related starter files for your project (Docker Inc.) Version: v1.0.1 Path: /Users/o_o/.docker/cli-plugins/docker-init sbom: View the packaged-based Software Bill Of Materials (SBOM) for an image (Anchore Inc.) Version: 0.6.0 Path: /Users/o_o/.docker/cli-plugins/docker-sbom scout: Docker Scout (Docker Inc.) Version: v1.5.0 Path: /Users/o_o/.docker/cli-plugins/docker-scout WARNING: Plugin "/Users/o_o/.docker/cli-plugins/docker-scan" is not valid: failed to fetch metadata: fork/exec /Users/o_o/.docker/cli-plugins/docker-scan: no such file or directory Server: Containers: 4 Running: 4 Paused: 0 Stopped: 0 Images: 4 Server Version: 25.0.3 Storage Driver: overlay2 Backing Filesystem: extfs Supports d_type: true Using metacopy: false Native Overlay Diff: true userxattr: false Logging Driver: json-file Cgroup Driver: cgroupfs Cgroup Version: 2 Plugins: Volume: local Network: bridge host ipvlan macvlan null overlay Log: awslogs fluentd gcplogs gelf journald json-file local splunk syslog Swarm: inactive Runtimes: io.containerd.runc.v2 runc Default Runtime: runc Init Binary: docker-init containerd version: ae07eda36dd25f8a1b98dfbf587313b99c0190bb runc version: v1.1.12-0-g51d5e94 init version: de40ad0 Security Options: seccomp Profile: unconfined cgroupns Kernel Version: 6.6.16-linuxkit Operating System: Docker Desktop OSType: linux Architecture: aarch64 CPUs: 10 Total Memory: 47.22GiB Name: docker-desktop ID: e0e4dcf7-742c-44b7-ad10-9f1fd4b7a3bd Docker Root Dir: /var/lib/docker Debug Mode: false HTTP Proxy: http.docker.internal:3128 HTTPS Proxy: http.docker.internal:3128 No Proxy: hubproxy.docker.internal Experimental: false Insecure Registries: hubproxy.docker.internal:5555 127.0.0.0/8 Live Restore Enabled: false WARNING: daemon is not using the default seccomp profile DOCKER COMPOSE V2 Docker Compose version v2.24.6-desktop.1 DOCKER-COMPOSE V1 Path to binary: /usr/local/bin/docker-compose Docker Compose version v2.24.6-desktop.1 PYGMY Path to binary: /opt/homebrew/bin/pygmy Using config file: /Users/o_o/.pygmy.yml Pygmy version vv0.12.0 AHOY Path to binary: /usr/local/bin/ahoy 2.0.2
Tried with ghcr.io/pygmystack/dnsmasq:pr-21 dnsmasq 2.86 and have confirmed that this version is the issue.
dnsmasq 2.86
Since upgrading to the latest pygmy images a couple of weeks ago, none of the URLs set through the
amazeio
network cannot resolve DNS.I was able to narrow this down to the following
pygmy
configuration that allowed me to isolate this particular image:Looking at the changes between this image versions: https://github.com/pygmystack/dnsmasq/compare/v0.0.1...v0.1.0#diff-dd2c0eb6ea5cfc6c4bd4eac30934e2d5746747af48fef6da689e85b752f39557R3
Looks like
dnsmasq-dnssec
was updated from2.85
to2.90
Here is a link to the changelog: https://thekelleys.org.uk/dnsmasq/CHANGELOG