On Saturday, January 12, 2019 at 5:57:19 PM UTC-8, Sam Whited wrote:
>
> On Fri, Jan 11, 2019, at 23:03, greg...@unity3d.com <javascript:> wrote: 
> > But now, I don't know how I can essentially copy the mod cache (or 
> > whatever the right term is) like I'd have copied the vendor directory. 
>
> If you're suggesting that you already have the module cached on the 
> machine that builds your containers, the cache lives at ~/go/pkg/mod by 
> default so you could probably copy that tree into your build container. 
>
> —Sam 
>

Thanks for help, folks. As far as copying the `go env GOPATH`/pkg/mod from 
the host to the docker container: I don't think I can copy from outside the 
"context", which is the project repository. It's not horribly important; 
this was more of an experiment for me to gain a bit more go.mod 
understanding.  For now, I'm just going back to vendoring 'till some of 
this shakes out a bit more.

-- 
You received this message because you are subscribed to the Google Groups 
"golang-nuts" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to golang-nuts+unsubscr...@googlegroups.com.
For more options, visit https://groups.google.com/d/optout.

Reply via email to