Docker Desktop Ubuntu 20.04 how to expose daemon

I’m trying to follow through labs/developer-tools/java/chapters/ch11-bigdata.adoc at master · docker/labs · GitHub this one and GitHub - fabianenardon/hadoop-docker-demo: A sample application with hadoop and docker sample requires io.fabric8:docker-maven-plugin to work which wants docker port to be available to connect.

export DOCKER_HOST="tcp://"

after that
mvn clean install -Papp-docker-image

and it throws
Cannot create docker access object : Cannot extract API version from server Connect to [/] failed: Connection refused (Connection refused) ->

Docker desktop created no dockerd and

{"hosts": ["tcp://", "unix:///var/run/docker.sock"]}

this won’t do the job either

sudo netstat -lntp | grep docker

returns ebuzer@DONE:~/git/docker hands on lab/hadoop-docker-demo/sample$ sudo netstat -lntp | grep docker tcp 0 0* LISTEN 6802/com.docker.bac

when i set

export DOCKER_HOST="tcp://"

and then
mvn clean install -Papp-docker-image

it returns

Cannot create docker access object : Cannot extract API version from server failed to respond -> [Help 1]

I search the internet and they say click expose daemon option in settings but my version doesn’t have it.

$ docker version
Client: Docker Engine - Community
 Cloud integration: v1.0.35+desktop.5
 Version:           20.10.7
 API version:       1.41
 Go version:        go1.13.15
 Git commit:        f0df350
 Built:             Wed Jun  2 11:56:47 2021
 OS/Arch:           linux/amd64
 Context:           desktop-linux
 Experimental:      true

Server: Docker Desktop 4.26.1 (131620)
  Version:          24.0.7
  API version:      1.43 (minimum version 1.12)
  Go version:       go1.20.10
  Git commit:       311b9ff
  Built:            Thu Oct 26 09:08:02 2023
  OS/Arch:          linux/amd64
  Experimental:     false
  Version:          1.6.25
  GitCommit:        d8f198a4ed8892c764191ef7b3b06d8a2eeb5c7f
  Version:          1.1.10
  GitCommit:        v1.1.10-0-g18a0cb0
  Version:          0.19.0
  GitCommit:        de40ad0

Docker needs to test their own documentation examples with new code so that there will be no regression like this one.