Andrew Stein

A followup note: I am not sure that even without golang sub-modules that the spec is reflective for golang. https://github.com/package-url/purl-spec#known-purl-types give the example ``` pkg:golang/github.com/gorilla/context@234fd47e07d1004f0aed9c ``` This implies that the...

@bradcupit I agree with your proposal — for go, there is not “namespace/name” concept. And if one is to drag submodules into the mix, there is no way to know,...

Also, as @jdillon has pointed out to me, the documentation sometimes uses "checksum" and sometimes "checksums"...

And @jdillon has further pointed out to me that near the top of the spec we have a docker example with > `pkg:docker/gcr.io/customer/dockerimage@sha256:244fd47e07d1004f0aed9c` and lower down we have > `pkg:docker/gcr.io/customer/dockerimage@sha256%3A244fd47e07d10`...

@robpike The preference for "golang" seems to be intentional. See this commit: https://github.com/package-url/purl-spec/commit/8e2e367cd60be444636b9f73b4b9306d06ae0f9d, but I do not have insight as to the reasoning

Some of my diagnostics: It seems that the `--driver` flag is not the issue here. Rather the first `--config` flag (to docker rather than to buildx) is causing the docker...

Further investigation done with @jflinchbaugh The following *does* work: ``` ~/.docker linux/amd64 linux/arm64 ``` After looking into it is seems that the `--config` argument to `docker`, in this case supplied...

I have found the same issue, but on Mac OX. I do not believe that it is related to the OS as @scanta2 implies but rather to the time zone...

The following is interesting: https://bugzilla.gnome.org/show_bug.cgi?id=137017