When adding a custom docker registry to a kubernetes cluster, image cache is ignored

[nicholasjackson]

When adding custom docker config to a kubernetes cluster, it seems to remove the default image cache and a cluster will fail to start unless internet is present.

resource "k8s_cluster" "k3s" {
  config {
    docker {
      no_proxy = [
        resource.container.registry.container_name,
        "auth-registry.demo.gs"
      ]
    }
  }

  network {
    id = resource.network.local.meta.id
  }
}

To Reproduce Create a cluster using the above stanza, with internet access Disconnect from the internet Attempt to recreate the cluster

Expected behavior The second run should create the cluster as the images have been cached however this does not happen