update pre-requsites to include checking docker is installed

[pavanstarmanwar]

Changes

• Add a line to check Docker is running

$ kind create cluster
ERROR: failed to create cluster: failed to list nodes: command "docker ps -a --filter label=io.x-k8s.kind.cluster=kind --format '{{.Names}}'" failed with error: exit status 1
Command Output: Cannot connect to the Docker daemon at unix:///Users/USER/.docker/run/docker.sock. Is the docker daemon running?
Ms-MacBook-Pro:~$ docker ps
Cannot connect to the Docker daemon at unix:///Users/USER/.docker/run/docker.sock. Is the docker daemon running?

After starting docker

Ms-MacBook-Pro:~$ kind create cluster
Creating cluster "kind" ...
 ✓ Ensuring node image (kindest/node:v1.25.3) 🖼 
 ✓ Preparing nodes 📦  
 ✓ Writing configuration 📜 
 ✓ Starting control-plane 🕹️ 
 ✓ Installing CNI 🔌 
 ✓ Installing StorageClass 💾 
Set kubectl context to "kind-kind"
You can now use your cluster with:

kubectl cluster-info --context kind-kind

Have a question, bug, or feature request? Let us know! https://kind.sigs.k8s.io/#community 🙂

Submitter Checklist

As the author of this PR, please check off the items in this checklist:

• Has Docs included if any changes are user facing
• Has Tests included if any functionality added or changed
• Follows the commit message standard
• Meets the Tekton contributor standards (including
  functionality, content, code)
• Has a kind label. You can add one by adding a comment on this PR that contains /kind <type>. Valid types are bug, cleanup, design, documentation, feature, flake, misc, question, tep
• Release notes block below has been updated with any user facing changes (API changes, bug fixes, changes requiring upgrade notices or deprecation warnings)
• Release notes contains the string "action required" if the change requires additional action from users switching to the new release

Release Notes

NONE

[linux-foundation-easycla]

The committers listed above are authorized under a signed CLA.

• ✅ login: pavanstarmanwar / name: pavan (1996546)

[tekton-robot]

Hi @pavanstarmanwar. Thanks for your PR.

I'm waiting for a tektoncd member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[jerop]

@pavanstarmanwar welcome to tekton!
/meow
/kind documentation
/ok-to-test

[tekton-robot]

@jerop:

In response to this:

@pavanstarmanwar welcome to tekton!
/meow
/kind documentation
/ok-to-test

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[pavanstarmanwar]

/assign @pritidesai

[pritidesai]

thank you @pavanstarmanwar for your contribution! Welcome to the tekton community 🎉

Please submit the checklist in the PR description. The additional check looks good to me.

I would suggest (a followup PR) to include an additional section troubleshooting in the end of the install.md to include what you have in the PR description i.e. before/after. Thanks!

[tekton-robot]

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: jerop

The full list of commands accepted by this bot can be found here.

The pull request process is described here

Needs approval from an approver in each of these files:

• OWNERS [jerop]

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pritidesai]

thank you @pavanstarmanwar 👍

/lgtm

[afrittoli]

Why only when running macOS? Why Docker?
This is a list of prerequisites for installing Tekton on Kubernetes - the first in the list is a Kubernetes cluster - the procedure is not really specific to where that kubernetes cluster is running.

[afrittoli]

Thank you @pavanstarmanwar for your contribution!

The old installation guide was referring to kind specifically, but not the current one.
In the current guide, the installation instructions start after a couple of paragraphs about setting up a local cluster (https://tekton.dev/docs/installation/local-installation/) which refer to the kind and minikube documentation directly.

The starting point for this document is a running k8s cluster, so I don't think that docker and troubleshooting about kind do not belong in it.

FYI @geriom @pritidesai

I would propose to revert this PR.

[geriom]

The starting point for this document is a running k8s cluster, so I don't think that docker and troubleshooting about kind do not belong in it.

I would propose to revert this PR.

I agree with you. This information is specifically about kind and should be covered by the Kind documentation.

I'm reverting the changes in #6172 which also adds a bunch of missing links.