Open diego-comlet opened 5 months ago
I think the issue could come from the differning ways Conda manages the SSL, and Poetry does internally
The following env variables, have been tried to no avail
REQUESTS_CA_BUNDLE=${CERT}
SSL_CERT_FILE=${CERT}
CURL_CA_BUNDLE=${CERT}
PIP_CERT=${CERT}
And also in a separate test
SSL_NO_VERIFY=1
@diego-comlet looks like CONDA_FLAGS="--insecure"
works as these get appended to the generated command line according to
Checklist
What happened?
For the given enviorment.yaml
After running conda-lock lock -f enviorment.yaml, the following issue is generated:
The conda env, is configured to ignore SSL certificates, but to not avail in this case
Conda Info
Conda Config
Conda list
Additional Context
Everyhing is running within a micromamba generated env.