core-dns does not support compression - need to edit config to make aws bucket resolution to work

[royire]

Description

trying to do curl https://<my_aws_bucket_name>.s3.eu-west-1.amazonaws.com/ was not working, looking at core-dns logs and saw dns: buffer size too small after running: kubectl edit configmap coredns -n kube-system and changing the relevant section to: (added force_tcp) forward . /etc/resolv.conf { force_tcp max_concurrent 1000 }

and then running: kubectl rollout restart -n kube-system deployment/coredns solved the issue

got the solution here: https://serverfault.com/questions/1145927/kubernetes-cluster-via-kubeadm-coredns-buffer-size-too-small-pods-network-pr

Reproduce

kubectl run dns-test --rm -i --tty --image busybox -- /bin/sh
curl https://<my-bucket>.s3.eu-west-1.amazonaws.com/
k logs deploy/coredns  -n kube-system
[ERROR] plugin/errors: 2 test-data.s3.eu-west-1.amazonaws.com. A: dns: buffer size too small
[ERROR] plugin/errors: 2 test-data.s3.eu-west-1.amazonaws.com. A: dns: buffer size too small
[ERROR] plugin/errors: 2 test-data.s3.eu-west-1.amazonaws.com. A: dns: buffer size too small
[ERROR] plugin/errors: 2 test-data.s3.eu-west-1.amazonaws.com. A: dns: buffer size too small

---

curl https://.s3.eu-west-1.amazonaws.com/ outside the container is working!!

Expected behavior

No response

docker version

Client:
 Cloud integration: v1.0.35+desktop.10
 Version:           25.0.2
 API version:       1.44
 Go version:        go1.21.6
 Git commit:        29cf629
 Built:             Thu Feb  1 00:18:45 2024
 OS/Arch:           darwin/arm64
 Context:           desktop-linux

Server: Docker Desktop 4.27.1 (136059)
 Engine:
  Version:          25.0.2
  API version:      1.44 (minimum version 1.24)
  Go version:       go1.21.6
  Git commit:       fce6e0c
  Built:            Thu Feb  1 00:23:21 2024
  OS/Arch:          linux/arm64
  Experimental:     false
 containerd:
  Version:          1.6.28
  GitCommit:        ae07eda36dd25f8a1b98dfbf587313b99c0190bb
 runc:
  Version:          1.1.12
  GitCommit:        v1.1.12-0-g51d5e94
 docker-init:
  Version:          0.19.0
  GitCommit:        de40ad0

docker info

Client:
 Version:    25.0.2
 Context:    desktop-linux
 Debug Mode: false
 Plugins:
  buildx: Docker Buildx (Docker Inc.)
    Version:  v0.12.1-desktop.4
    Path:     /Users/royireshef/.docker/cli-plugins/docker-buildx
  compose: Docker Compose (Docker Inc.)
    Version:  v2.24.3-desktop.1
    Path:     /Users/royireshef/.docker/cli-plugins/docker-compose
  debug: Get a shell into any image or container. (Docker Inc.)
    Version:  0.0.22
    Path:     /Users/royireshef/.docker/cli-plugins/docker-debug
  dev: Docker Dev Environments (Docker Inc.)
    Version:  v0.1.0
    Path:     /Users/royireshef/.docker/cli-plugins/docker-dev
  extension: Manages Docker extensions (Docker Inc.)
    Version:  v0.2.21
    Path:     /Users/royireshef/.docker/cli-plugins/docker-extension
  feedback: Provide feedback, right in your terminal! (Docker Inc.)
    Version:  v1.0.4
    Path:     /Users/royireshef/.docker/cli-plugins/docker-feedback
  init: Creates Docker-related starter files for your project (Docker Inc.)
    Version:  v1.0.0
    Path:     /Users/royireshef/.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/royireshef/.docker/cli-plugins/docker-sbom
  scout: Docker Scout (Docker Inc.)
    Version:  v1.3.0
    Path:     /Users/royireshef/.docker/cli-plugins/docker-scout
WARNING: Plugin "/Users/royireshef/.docker/cli-plugins/docker-scan" is not valid: failed to fetch metadata: fork/exec /Users/royireshef/.docker/cli-plugins/docker-scan: no such file or directory

Server:
 Containers: 69
  Running: 63
  Paused: 0
  Stopped: 6
 Images: 92
 Server Version: 25.0.2
 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.12-linuxkit
 Operating System: Docker Desktop
 OSType: linux
 Architecture: aarch64
 CPUs: 8
 Total Memory: 19.26GiB
 Name: docker-desktop
 ID: 41094108-242b-48fb-b8a2-b44f8c1e7d18
 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

Diagnostics ID

ACA17ACC-D214-48B8-9108-A0C9042749D9/20240214125527

Additional Info

No response

[dgageot]

Hi @royire! is it something that used to work with previous versions of Docker Desktop?

[royire]

yes it is, it is now happening to almost all of our developers upgrading to the latest macos major and docker > 4.24

[dgageot]

cc @djs55

[dgageot]

@royire do you have a quick repro that doesn't involve k8s?

[mschfh]

looks like a duplicate of #7088?