As the dot is currently included in the backticks in the docs, this suggests that it should be included in the commend that should be executed as well. However, this would be incorrect, as it would result in a path that would end with a dot as well.
I put the dot after the backticks to make it clear it doesn't belong to the command. As the dot was always present in other similar instances in the docs I kept it, but if it wasn't for consistency I would be inclined to remove it entirely to make it even more foolproof.
Comment From: pivotal-cla
@martinfrancois Please sign the Contributor License Agreement!
Click here to manually synchronize the status of this Pull Request.
See the FAQ for frequently asked questions.
Comment From: pivotal-cla
@martinfrancois Thank you for signing the Contributor License Agreement!
Comment From: philwebb
Thanks @martinfrancois, for even more clarity we could do something like this:
The plugin can communicate with the Docker daemon provided by https://github.com/abiosoft/colima[Colima].
The `DOCKER_HOST` environment variable can be set by using the following command:
[source,shell,subs="verbatim,attributes"]
----
$ export DOCKER_HOST=$(docker context inspect colima -f '{{.Endpoints.docker.Host}}')
----
What do you think? Are you interested in updating your PR?
Comment From: martinfrancois
You're welcome, and thanks as well @philwebb, I really like the idea, makes it even clearer without introducing inconsistencies. I changed it as you suggested.
Comment From: philwebb
Thanks again @martinfrancois, this has now been merged.