fd0708286c
We check python files with dib-lint rather than flake8 which have conflicting opinions. This means weve been (forcibly) writing non pep8 python. Also fixing pep8 issues so tests pass. Change-Id: Idc9db40334f6e15738a7802c06697270df68741c |
||
---|---|---|
.. | ||
extra-data.d | ||
post-install.d | ||
pre-install.d | ||
README.md |
Inject a PyPI mirror
Use a custom PyPI mirror to build images. The default is to bind mount one from ~/.cache/image-create/pypi/mirror into the build environment as mirror URL file:///tmp/pypi. The element temporarily overwrites /root/.pip.conf and .pydistutils.cfg to use it.
When online, the official pypi.python.org pypi index is supplied as an extra-url, so uncached dependencies will still be available. When offline, only the mirror is used - be warned that a stale mirror will cause build failures. To disable the pypi.python.org index without using --offline (e.g. when working behind a corporate firewall that prohibits pypi.python.org) set DIB_NO_PYPI_PIP to any non-empty value.
To use an arbitrary mirror set PYPI_MIRROR_URL=http[s]://somevalue/
Additional mirrors can be added by exporting PYPI_MIRROR_URL_1=... etc. Only the one mirror can be used by easy-install, but since wheels need to be in the first mirror to be used, the last listed mirror is used as the pydistutils index. NB: The sort order for these variables is a simple string sort - if you have more than 9 additional mirrors, some care will be needed.
A typical use of this element is thus: export PYPI_MIRROR_URL=http://site/pypi/Ubuntu-13.10 export PYPI_MIRROR_URL_1=http://site/pypi/ export PYPI_MIRROR_URL_2=file:///tmp/pypi
devpi-server can be useful in making a partial PyPI mirror suitable for building images. For instance:
-
pip install -U devpi
-
devpi-server quickstart
-
devpi use http://machinename:3141
-
Re-export your variables to point at the new mirror:
export PYPI_MIRROR_URL=http://machinename:3141/ unset PYPI__MIRROR_URL_1 unset PYPI__MIRROR_URL_1
The next time packages are installed, they'll be cached on the local devpi server; subsequent runs pointed at the same mirror will use the local cache if the upstream can't be contacted.
Note that this process only has the server running temporarily; see Quickstart: Permanent install on server/laptop guide from the devpi developers for more information on a more permanent setup.