driver-go | taos go driver

From the comments, your docker command was aliased to sudo docker. The sudo command will not pass through the environment variables defined by docker-machine so it will default back to the /var/lib/docker.sock.

As for which vs type, which will point to a binary in the $PATH to let you know where something is located. type will let you know how the shell is running that command including shell built-ins, any aliases, or function definitions.

To solve this, remove the alias from your bash scripts and launch a new shell. In an existing shell that has the alias, you can run unalias docker or /usr/local/bin/docker (with the full path). In environments where you used sudo, consider adding the user to the docker group with:

sudo usermod -aG docker `whoami` && newgrp docker

That will give you group level access to the docker socket so you don't need to run sudo for the docker commands.