Kevin Leimkuhler d3c950d682 Add install error for runtime container check (#7468) ... When installing Linkerd on a cluster with the Docker container runtime, `proxyInit.runAsRoot` but be set to `true` in order for Linkerd to operate. This is checked two different ways: `linkerd check --pre` and `linkerd check`. #7457 discussed if it's better to emit this as a warning or error, but after some further discussion it makes more sense as a `linkerd install` runtime error so that a user cannot miss this configuration. It still remains as part of `linkerd check` in case more nodes are added that do not satisfy this condition, or Linkerd is installed through Helm. ```sh $ linkerd install there are nodes using the docker container runtime and proxy-init container must run as root user. try installing linkerd via --set proxyInit.runAsRoot=true $ linkerd install --set proxyInit.runAsRoot=false there are nodes using the docker container runtime and proxy-init container must run as root user. try installing linkerd via --set proxyInit.runAsRoot=true $ linkerd install --set proxyInit.runAsRoot="" there are nodes using the docker container runtime and proxy-init container must run as root user. try installing linkerd via --set proxyInit.runAsRoot=true $ linkerd install --set proxyInit.runAsRoot=true ... $ linkerd install --set proxyInit.runAsRoot=1 ... ``` Signed-off-by: Kevin Leimkuhler <kleimkuhler@icloud.com>		2021-12-20 12:08:44 -05:00
..
testdata	Add install error for runtime container check (#7468)	2021-12-20 12:08:44 -05:00
uninstall_test.go	Increase all testing timeouts to 60 minutes (#6134)	2021-05-17 16:49:57 -04:00