Merge pull request #456 from kubernetes-sigs/bugfix/manifest-image-perms

Fix issue generating manifests due to Docker perms

Author: k8s-ci-robot

docs/getting_started.md

@@ -94,6 +94,7 @@ With the above environment variable file it is now possible to generate the mani
 
 ```shell
 $ docker run --rm \
+  --user "$(id -u):$(id -g)" \
   -v "$(pwd)/management-cluster":/out \
   -v "$(pwd)/envvars.txt":/out/envvars.txt:ro \
   gcr.io/cluster-api-provider-vsphere/release/manifests:latest \
@@ -142,6 +143,7 @@ Using the same Docker command as above, generate resources for a new cluster, th
 
 ```shell
 docker run --rm \
+  --user "$(id -u):$(id -g)" \
   -v "$(pwd)/workload-cluster-1":/out \
   -v "$(pwd)/envvars.txt":/out/envvars.txt:ro \
   gcr.io/cluster-api-provider-vsphere/release/manifests:latest \

hack/tools/generate-yaml/Dockerfile

@@ -49,6 +49,9 @@ COPY ./vendor/sigs.k8s.io/cluster-api/config ./vendor/sigs.k8s.io/cluster-api/co
 # Copy in the examples directory.
 COPY ./cmd/clusterctl/examples/vsphere/*.template ./cmd/clusterctl/examples/vsphere/
 
+# Ensure all the directories in the /build directory are writeable.
+RUN find . -type d -exec chmod 0777 \{\} \;
+
 # This build arg specifies the value of the -m flag for generate-yaml.sh, the
 # CAPV manager image inserted into the generated provider components.
 ARG CAPV_MANAGER_IMAGE=gcr.io/cluster-api-provider-vsphere/ci/manager:latest