-
Notifications
You must be signed in to change notification settings - Fork 41
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Explore using conda-lock
to generate lockfiles
#74
Comments
An alternative to
These spec files would later be able to be used directly to replicate the environment in different machines: > conda create --name gds --file gds_py-<architecture>-<os>-<platform>.txt One major drawback of this approach is the end-user needs to know their architecture/OS/platform to select the appropriate install file. |
Arch's to be supported (and write explicit files for):
|
conda-lock
provides the ability to generate lockfiles for different platforms. This would be a great addition to replace the currentlygds_py.yml
as a way to build the same Python environment as the container natively.An idea of how this could work:
gds_py
environment on DockerfileIf the workflow above can work, then we should add CI testing on each architecture.
The text was updated successfully, but these errors were encountered: