Re: Docker builds, ~/.pip/cache, and O(1) or O(n) bandwidth

You can use a local PyPI mirror, e.g. devpi, and point your docker builds
at that, basically tricking docker by going through the (local) network
stack instead of the filesystem.

On Tue, May 7, 2019 at 8:12 AM Wes Turner <[email protected]> wrote:

> What is the best way to build docker images without constantly
> re-downloading packages from PyPI (to use ~O(1) bandwidth instead of O(n)
> for every build)
>
> (AFAIK, nobody has any issue with the amount of bandwidth PyPI uses)
>
> Thus far, Docker doesn't want to support a build-time -v option (that
> could be used to bind-mount .pip/cache in at build time):
>
> "build time only -v option"
> https://github.com/moby/moby/issues/14080
>
> Buildah *does* support a build-time -v option (and can also do rootless
> builds without a docker socket)
> --
> Distutils-SIG mailing list -- [email protected]
> To unsubscribe send an email to [email protected]
> https://mail.python.org/mailman3/lists/distutils-sig.python.org/
> Message archived at
> https://mail.python.org/archives/list/[email protected]/message/IL6MGTSAA4X5UZDERCAAAFGGX5DGRPF3/
>

--
Distutils-SIG mailing list -- [email protected]
To unsubscribe send an email to [email protected]
https://mail.python.org/mailman3/lists/distutils-sig.python.org/
Message archived at https://mail.python.org/archives/list/[email protected]/message/2MNMGYBNFOOVGXA2JQ2PLDTZITZXANJU/