This isn't a request for a code change as much as for documentation, presuming that there is in fact a reasonable way to reuse the ./cache directory for arbitrary user-provided content from inside the container. If there isn't, then this might be into feature-request territory (which I'd be happy to take a shot at if given some guidance about what an implementation would look like).
Insofar as oci-build-task uses Buildkit, extended syntax is available in Dockerfiles using it; for example:
RUN --mount=type=cache,target=/go-cache env GOCACHE=/go-cache go build
(similar use cases include Maven jar caches, Nix store caches, etc).
Unfortunately, even with caches: [{"path": "cache"}] enabled, this doesn't actually work to reuse downloaded Go modules across builds -- there's an error of the form:
(*service).Write failed error="rpc error: code = Canceled desc = context canceled
...and as far as I can tell, the ./cache directory isn't mapped into the container context.
Is there a reasonable way to cache content inside of oci-build-task?
This isn't a request for a code change as much as for documentation, presuming that there is in fact a reasonable way to reuse the
./cachedirectory for arbitrary user-provided content from inside the container. If there isn't, then this might be into feature-request territory (which I'd be happy to take a shot at if given some guidance about what an implementation would look like).Insofar as oci-build-task uses Buildkit, extended syntax is available in Dockerfiles using it; for example:
RUN --mount=type=cache,target=/go-cache env GOCACHE=/go-cache go build(similar use cases include Maven jar caches, Nix store caches, etc).
Unfortunately, even with
caches: [{"path": "cache"}]enabled, this doesn't actually work to reuse downloaded Go modules across builds -- there's an error of the form:...and as far as I can tell, the
./cachedirectory isn't mapped into the container context.Is there a reasonable way to cache content inside of oci-build-task?