I am testing the Windows based T2G workshop config process. Also using the new powershell script equivalents recently added by @corn-pivotal.
I have completed all OS level prereqs and also successfully ran the download-dependencies.ps1 script.
I'm running Windows10 with latest docker desktop installed and configured to use WSL2 (using ubuntu 20.04 as default WSL subsystem)
First issue:
The tanzu standalone create tce --cni=calico errors because the Tanzu CLI can't understand "standalone". This does work on my mac based T2G setup so seems to be a windows specific thing...?
PS C:\Users\Chris Almond\tanzu-to-go-workshop> tanzu standalone create tce --cni=calico
Error: unknown command "standalone" for "tanzu"
Did you mean this?
standalone-cluster
Using tanzu standalone-cluster create tce --cni=calico fixed above but leads to a second problem...
Ok looks like in the slack channel there may be work arounds for this: use a v0.10.x version of Tanzu, workaround for the certififcate issue etc. I don't see anything in our repo doc on this yet though.
I am testing the Windows based T2G workshop config process. Also using the new powershell script equivalents recently added by @corn-pivotal.
I have completed all OS level prereqs and also successfully ran the download-dependencies.ps1 script.
I'm running Windows10 with latest docker desktop installed and configured to use WSL2 (using ubuntu 20.04 as default WSL subsystem)
First issue:
The
tanzu standalone create tce --cni=calico
errors because the Tanzu CLI can't understand "standalone". This does work on my mac based T2G setup so seems to be a windows specific thing...?Using
tanzu standalone-cluster create tce --cni=calico
fixed above but leads to a second problem...Second issue:
Checking tanzu command line help for this running tanzu cli windows version shows no flag available for
-c
or--cni=