[X] My problem is not solved in the Troubleshooting docs
Anaconda default channels
[X] I do NOT use the Anaconda default channels (pkgs/* etc.)
How did you install Mamba?
Micromamba
Search tried in issue tracker
is:issue "offline", is:issue in:title "offline"
Latest version of Mamba
[X] My problem is not solved with the latest version
Tried in Conda?
Not applicable
Describe your issue
I have a situation where I need to install an environment on a machine without internet access (Windows machine). My plan is to use micromamba since it is statically linked and I like using it anyway. I am trying to only download the packages required on an online machine (also Windows) and then move them to the offline machine, where I would install them. My environment is defined in an environment.yml (posted below).
I'm trying to do this very bare-bones from a blank slate. I have no rc file defined. After making micromamba.exe available on my PATH, these are the steps I've taken:
Navigate to my project root, where all that exists is environment.yml
This is the point at which I would move everything in .micromamba over to the offline machine, which I'm simulating by closing my terminal, unplugging my ethernet, and re-opening my project root.
conda-forge/win-64 Using cache
conda-forge/noarch Using cache
critical libmamba Specified pkgs_dir does not exist
I thought maybe activating the environment would help but it does not. If I manually define my pkgs_dirs in $env:MAMBA_ROOT_PREFIX\.mambarc then I am able to install, but I am confused as to why I would have to do that when, from the documentation:
This cache is shared by all environments or target prefixes based on the same root prefix. Basically, that cache directory is a subdirectory located at $root_prefix/pkgs/.
If I have my root prefix defined, and have confirmed that all my packages do exist in $env:MAMBA_ROOT_PREFIX\pkgs, then why isn't micromamba pulling from there automatically?
Troubleshooting docs
Anaconda default channels
How did you install Mamba?
Micromamba
Search tried in issue tracker
is:issue "offline", is:issue in:title "offline"
Latest version of Mamba
Tried in Conda?
Not applicable
Describe your issue
I have a situation where I need to install an environment on a machine without internet access (Windows machine). My plan is to use
micromamba
since it is statically linked and I like using it anyway. I am trying to only download the packages required on an online machine (also Windows) and then move them to the offline machine, where I would install them. My environment is defined in anenvironment.yml
(posted below).I'm trying to do this very bare-bones from a blank slate. I have no rc file defined. After making
micromamba.exe
available on my PATH, these are the steps I've taken:environment.yml
mkdir .micromamba
$env:MAMBA_ROOT_PREFIX="$PWD\.micromamba"
micromamba create -n testenv
micromamba install --download-only -f environment.yml
.micromamba
over to the offline machine, which I'm simulating by closing my terminal, unplugging my ethernet, and re-opening my project root.$env:MAMBA_ROOT_PREFIX="$PWD\.micromamba"
micromamba install --offline -f environment.yml
ReturnsI thought maybe activating the environment would help but it does not. If I manually define my
pkgs_dirs
in$env:MAMBA_ROOT_PREFIX\.mambarc
then I am able to install, but I am confused as to why I would have to do that when, from the documentation:If I have my root prefix defined, and have confirmed that all my packages do exist in
$env:MAMBA_ROOT_PREFIX\pkgs
, then why isn'tmicromamba
pulling from there automatically?mamba info / micromamba info
Logs
environment.yml
~/.condarc