Pack build on windows fails when using --report-output-dir

[tomkennedy513]

Summary

When running pack build with the --report-output-dir flag on windows, I get a no such container error:

ERROR: failed to build: executing lifecycle: Error: No such container:path: 14975acacb3073150076a8e713e40b5975ff09ebc9ad9bc0ad4c1bbf9287f76c:c:\layers\report.toml

---

Reproduction

Steps

I ran this command on a windows github action runner

pack build gcr.io/cf-build-service-public/kpack-dev/build-init-windows \
--builder gcr.io/dotnet-build-gcp/go-multios/builder-windows \
 --env BP_GO_LDFLAGS="-X 'github.com/pivotal/kpack/cmd.Version=dev' -X 'github.com/pivotal/kpack/cmd.Commit=some-commit'" \
--env BP_GO_TARGETS=".\cmd\build-init;.\cmd\network-wait-launcher" \
--report-output-dir . \
--cache-image gcr.io/cf-build-service-public/kpack-dev/build-init-windows-cache \
--publish --trust-builder

Current behavior

I got an error ERROR: failed to build: executing lifecycle: Error: No such container:path: 14975acacb3073150076a8e713e40b5975ff09ebc9ad9bc0ad4c1bbf9287f76c:c:\layers\report.toml

Expected behavior

I expected the report.toml to be saved to the runner like it does with Linux

---

Environment

This is running on a windows-2019 GHA runner with pack v0.29.0 installed

[joe-kimmel-vmw]

Thanks for filing this bug report!

I looked into this a little and it seemed to me that I was able to reproduce it with a simple windows build and that both the sbom output dir and reports output dir flags were broken, but I wasn't able to quickly find a root cause or solution.