Discussion:
[conda] Caching a conda installation
Michael Milton
2018-09-19 23:46:59 UTC
Permalink
I'm using conda (miniconda) packages as part of my CI build, so to speed
things up I want to cache the entire conda environment so that it doesn't
have to install every time. To this end, I save /opt/conda (which is where
conda is installed in the continuumio/miniconda Docker image
<https://hub.docker.com/r/continuumio/miniconda/>) to a cache location, and
restore this cache at the start of each build.

However, if I restore that cache in a build and then run the `conda
install` command again, I get two issues:

- It doesn't seem to detect that all these packages are already
installed, and I get "The following NEW packages will be INSTALLED"
message, followed by an attempted installation.
- When conda tries to actually install these packages, I get hundreds of
errors saying things like:

CondaVerificationError: The package for openssl located at
/opt/conda/pkgs/openssl-1.0.2p-h14c3975_0
appears to be corrupted. The path 'ssl/man/man3/ASN1_OBJECT_free.3'
specified in the package manifest cannot be found.

CondaVerificationError: The package for openssl located at
/opt/conda/pkgs/openssl-1.0.2p-h14c3975_0
appears to be corrupted. The path 'ssl/man/man3/ASN1_STRING_print_ex.3'
specified in the package manifest cannot be found.


Why is this happening? How should I be caching a conda environment (without
having to re-install all of these packages each time)? Am I missing another
folder that I should also be caching?

Thanks.
--
You received this message because you are subscribed to the Google Groups "conda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to conda+***@continuum.io.
To post to this group, send email to ***@continuum.io.
Visit this group at https://groups.google.com/a/continuum.io/group/conda/.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/conda/e4664832-8994-4e67-9b2d-d73d78dcf87b%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.
Michael Milton
2018-09-20 00:15:31 UTC
Permalink
I don't know if I can check for sure, but this is in AWS CodeBuild so I
doubt they would use an unconventional filesystem.
--
You received this message because you are subscribed to the Google Groups "conda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to conda+***@continuum.io.
To post to this group, send email to ***@continuum.io.
Visit this group at https://groups.google.com/a/continuum.io/group/conda/.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/conda/a3812acf-a312-401a-a24d-36611e895692%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.
Michael Milton
2018-09-20 00:21:04 UTC
Permalink
Alternatively, since this doesn't seem to work, is there a package cache of
tarballs I could cache instead? Equivalent to Pip's ~/.cache/pip.
--
You received this message because you are subscribed to the Google Groups "conda - Public" group.
To unsubscribe from this group and stop receiving emails from it, send an email to conda+***@continuum.io.
To post to this group, send email to ***@continuum.io.
Visit this group at https://groups.google.com/a/continuum.io/group/conda/.
To view this discussion on the web visit https://groups.google.com/a/continuum.io/d/msgid/conda/d57639df-dc0c-453c-8e77-054870ec6751%40continuum.io.
For more options, visit https://groups.google.com/a/continuum.io/d/optout.
Loading...