`dind` service deprecation warnings

Looking over the Docker Compose logs, I found these warinigs:

dind-1  | time="2026-05-28T11:37:59.019673904Z" level=warning msg="Binding to IP address without --tlsverify is insecure and gives root access on this machine to everyone who has access to your network." host="tcp://0.0.0.0:2375"
dind-1  | time="2026-05-28T11:37:59.019681004Z" level=warning msg="Binding to an IP address, even on localhost, can also give access to scripts run in a browser. Be safe out there!" host="tcp://0.0.0.0:2375"
dind-1  | time="2026-05-28T11:37:59.019683934Z" level=warning msg="[DEPRECATION NOTICE] In future versions this will be a hard failure preventing the daemon from starting! Learn more at: https://docs.docker.com/go/api-security/" host="tcp://0.0.0.0:2375"
dind-1  | time="2026-05-28T11:38:00.020735521Z" level=warning msg="Binding to an IP address without --tlsverify is deprecated. Startup is intentionally being slowed down to show this message" host="tcp://0.0.0.0:2375"
dind-1  | time="2026-05-28T11:38:00.020766471Z" level=warning msg="Please consider generating tls certificates with client validation to prevent exposing unauthenticated root access to your network" host="tcp://0.0.0.0:2375"

I think it's a good advanced heads-up warning to track.

Start by locating the Docker Compose configuration for the dind service and reviewing how it exposes the Docker daemon on tcp://0.0.0.0:2375. Read the linked Docker API security guidance and verify that the completed change removes the deprecation warnings without breaking Compose clients that use the service.