docker based mgmt cluster: failed to create provider object cert-manager.io/v1alpha2

[vxav]

Started management cluster creation in docker with:
tanzu management-cluster create -i docker --name testanzu -v 10 --plan dev --ceip-participation=false

Fails during creation.

[...]
Installing cert-manager Version="v1.1.0"

Waiting for cert-manager to be available...

Installing Provider="cluster-api" Version="v0.3.23" TargetNamespace="capi-system"

Deleting kind cluster: tkg-kind-c5dik324lppqhnhj1qd0

Error: unable to set up management cluster: unable to initialize providers: action failed after 10 attempts: failed to create provider object cert-manager.io/v1alpha2, Kind=Certificate, capi-webhook-system/capi-serving-cert: conversion webhook for cert-manager.io/v1alpha2, Kind=Certificate failed: Post "https://cert-manager-webhook.cert-manager.svc:443/convert?timeout=30s": x509: certificate signed by unknown authority, this can be possible because of the outbound connectivity issue. Please check deployed nodes for outbound connectivity.

[github-actions]

Hey @vxav! Thanks for opening your first issue. We appreciate your contribution and welcome you to our community! We are glad to have you here and to have your input on Tanzu Community Edition.

[joshrosso]

Hey @vxav! We'd love to help you troubleshoot this further.

A few options:

• Join us in #tanzu-community-edition and we could better understand the environment (machine) you're deploying to.
• Checkout our bootstrap troubleshooting docs
• Tell us more about the bootstrapping process
  • what kind of machine are you trying to deploy to
  • what are you docker resource setting set to
  • what command did you run
  • what are the full logs you saw

[vxav]

Excellent point there -> "what are you docker resource setting set to"
I was using an all purpose debian vm lying around that was waaay underprovisioned and didn't pay attention to it. Another one for the old RTFM.
Well, at least you can link that error to a lack of resources :)
Thanks for picking it up !

[davidvonthenen]

looks like this has been resolved. if that isn't the case, please reopen and we can follow up with this.