InformationIt is possible to make the Docker daemon to listen on a specific IP and port and any other Unix socket other than default Unix socket. Configure TLS authentication to restrict access to Docker daemon via IP and port.
By default, Docker daemon binds to a non-networked Unix socket and runs with 'root' privileges. If you change the default docker daemon binding to a TCP port or any other Unix socket, anyone with access to that port or socket can have full access to Docker daemon and in turn to the host system. Hence, you should not bind the Docker daemon to another IP/port or a Unix socket.
If you must expose the Docker daemon via a network socket, configure TLS authentication for the daemon and Docker Swarm APIs (if using).This would restrict the connections to your Docker daemon over the network to a limited number of clients who could successfully authenticate over TLS.
SolutionFollow the steps mentioned in the Docker documentation or other references.
You would need to manage and guard certificates and keys for Docker daemon and Docker clients.
By default, TLS authentication is not configured.