[X] I searched open reports and couldn't find a duplicate
What happened?
I'm trying to create a reproducible environment from an existing environment. What I'm trying to do is create a lockfile for a docker container that already has conda installed (it's a pytorch image). When I try to lock the environment it ends up updating existing dependencies, including e.g. python and pytorch. Which isn't good for a pytorch image.
What I'm expecting:
specifying a lockfile, should freeze some or all of the dependency version to their current version, unless requesting an upgrade
How I'm reproducing it:
docker run -it pytorch/pytorch:1.12.1-cuda11.3-cudnn8-devel conda list --explicit > conda-linux-64.lock
conda lock -k explicit -f environment.yml
Forgive me if the problem is invocation, but the console seems to show that it's parsed the lockfile, but when I look at the values, many of the core packages like python and pytorch have different versions than what I started with.
Conda Info
active environment : None
user config file : /root/.condarc
populated config files :
conda version : 4.13.0
conda-build version : 3.21.9
python version : 3.7.13.final.0
virtual packages : __linux=5.15.49=0
__glibc=2.27=0
__unix=0=0
__archspec=1=x86_64
base environment : /opt/conda (writable)
conda av data dir : /opt/conda/etc/conda
conda av metadata url : None
channel URLs : https://repo.anaconda.com/pkgs/main/linux-64
https://repo.anaconda.com/pkgs/main/noarch
https://repo.anaconda.com/pkgs/r/linux-64
https://repo.anaconda.com/pkgs/r/noarch
package cache : /opt/conda/pkgs
/root/.conda/pkgs
envs directories : /opt/conda/envs
/root/.conda/envs
platform : linux-64
user-agent : conda/4.13.0 requests/2.27.1 CPython/3.7.13 Linux/5.15.49-linuxkit ubuntu/18.04.6 glibc/2.27
UID:GID : 0:0
netrc file : None
offline mode : False
I want to install more packages into a docker container in a reproducible way. Ideally I just want a way to lock an environment with specific constraints pre-determined. Possibly there should be a way to pass any of [--freeze-installed | --update-deps | -S | --update-all | --update-specs] to conda-lock
Checklist
What happened?
I'm trying to create a reproducible environment from an existing environment. What I'm trying to do is create a lockfile for a docker container that already has conda installed (it's a pytorch image). When I try to lock the environment it ends up updating existing dependencies, including e.g. python and pytorch. Which isn't good for a pytorch image.
What I'm expecting: specifying a lockfile, should freeze some or all of the dependency version to their current version, unless requesting an upgrade
How I'm reproducing it:
Forgive me if the problem is invocation, but the console seems to show that it's parsed the lockfile, but when I look at the values, many of the core packages like python and pytorch have different versions than what I started with.
Conda Info
Conda Config
No response
Conda list
Additional Context
I want to install more packages into a docker container in a reproducible way. Ideally I just want a way to lock an environment with specific constraints pre-determined. Possibly there should be a way to pass any of
[--freeze-installed | --update-deps | -S | --update-all | --update-specs]to conda-lock