How to transfer Anaconda env installed on one machine to another? [Both with Ubuntu installed]
i have been using Anaconda(4.3.23)
on my GuestOS ubuntu 14.04
which is installed on Vmware on HostOS windows 8.1
. i have setup an environment in anaconda and have installed many libraries, some of which were very hectic to install (not straight forward pip installs). few libraries had inner dependencies and had to be build together and from their git source.
Problem
i am going to use Cloud based VM (Azure GPU instance) to use GPU. but i don't want to get into the hectic installation again as i don't want to waste money on the time it will take me to install all the packages and libraries again
Is there any way to transfer/copy my existing env (which has everything already installed) to the Cloud VM.?
python ubuntu anaconda virtualenv conda
add a comment |
i have been using Anaconda(4.3.23)
on my GuestOS ubuntu 14.04
which is installed on Vmware on HostOS windows 8.1
. i have setup an environment in anaconda and have installed many libraries, some of which were very hectic to install (not straight forward pip installs). few libraries had inner dependencies and had to be build together and from their git source.
Problem
i am going to use Cloud based VM (Azure GPU instance) to use GPU. but i don't want to get into the hectic installation again as i don't want to waste money on the time it will take me to install all the packages and libraries again
Is there any way to transfer/copy my existing env (which has everything already installed) to the Cloud VM.?
python ubuntu anaconda virtualenv conda
You should be able to doconda list --export > requirements.txt
and then on your new environment doconda create --name [env name] --file requirements.txt
– gobrewers14
Aug 24 '17 at 14:53
wouldn't that only work if the packages and libraries are out of the shelf and to be installed from pip?. by your method i will have the name list of packages. and in new env those packages will be installed from pip again. but the problem is i have custom built packages which had dependent configurations with each other
– Qaisar Rajput
Aug 24 '17 at 15:00
add a comment |
i have been using Anaconda(4.3.23)
on my GuestOS ubuntu 14.04
which is installed on Vmware on HostOS windows 8.1
. i have setup an environment in anaconda and have installed many libraries, some of which were very hectic to install (not straight forward pip installs). few libraries had inner dependencies and had to be build together and from their git source.
Problem
i am going to use Cloud based VM (Azure GPU instance) to use GPU. but i don't want to get into the hectic installation again as i don't want to waste money on the time it will take me to install all the packages and libraries again
Is there any way to transfer/copy my existing env (which has everything already installed) to the Cloud VM.?
python ubuntu anaconda virtualenv conda
i have been using Anaconda(4.3.23)
on my GuestOS ubuntu 14.04
which is installed on Vmware on HostOS windows 8.1
. i have setup an environment in anaconda and have installed many libraries, some of which were very hectic to install (not straight forward pip installs). few libraries had inner dependencies and had to be build together and from their git source.
Problem
i am going to use Cloud based VM (Azure GPU instance) to use GPU. but i don't want to get into the hectic installation again as i don't want to waste money on the time it will take me to install all the packages and libraries again
Is there any way to transfer/copy my existing env (which has everything already installed) to the Cloud VM.?
python ubuntu anaconda virtualenv conda
python ubuntu anaconda virtualenv conda
asked Aug 24 '17 at 14:44
Qaisar RajputQaisar Rajput
350214
350214
You should be able to doconda list --export > requirements.txt
and then on your new environment doconda create --name [env name] --file requirements.txt
– gobrewers14
Aug 24 '17 at 14:53
wouldn't that only work if the packages and libraries are out of the shelf and to be installed from pip?. by your method i will have the name list of packages. and in new env those packages will be installed from pip again. but the problem is i have custom built packages which had dependent configurations with each other
– Qaisar Rajput
Aug 24 '17 at 15:00
add a comment |
You should be able to doconda list --export > requirements.txt
and then on your new environment doconda create --name [env name] --file requirements.txt
– gobrewers14
Aug 24 '17 at 14:53
wouldn't that only work if the packages and libraries are out of the shelf and to be installed from pip?. by your method i will have the name list of packages. and in new env those packages will be installed from pip again. but the problem is i have custom built packages which had dependent configurations with each other
– Qaisar Rajput
Aug 24 '17 at 15:00
You should be able to do
conda list --export > requirements.txt
and then on your new environment do conda create --name [env name] --file requirements.txt
– gobrewers14
Aug 24 '17 at 14:53
You should be able to do
conda list --export > requirements.txt
and then on your new environment do conda create --name [env name] --file requirements.txt
– gobrewers14
Aug 24 '17 at 14:53
wouldn't that only work if the packages and libraries are out of the shelf and to be installed from pip?. by your method i will have the name list of packages. and in new env those packages will be installed from pip again. but the problem is i have custom built packages which had dependent configurations with each other
– Qaisar Rajput
Aug 24 '17 at 15:00
wouldn't that only work if the packages and libraries are out of the shelf and to be installed from pip?. by your method i will have the name list of packages. and in new env those packages will be installed from pip again. but the problem is i have custom built packages which had dependent configurations with each other
– Qaisar Rajput
Aug 24 '17 at 15:00
add a comment |
2 Answers
2
active
oldest
votes
From the very end of this documentation page:
Save packages for future use:
conda list --export > package-list.txt
Reinstall packages from an export file:
conda create -n myenv --file package-list.txt
add a comment |
If conda list --export
failes like this ...
Executing conda list --export > package-list.txt
creates a file which looks like this:
# This file may be used to create an environment using:
# $ conda create --name <env> --file <this file>
# platform: win-64
_tflow_1100_select=0.0.1=gpu
absl-py=0.5.0=py_0
astor=0.7.1=py_0
...
But creating a new environment by executing conda create -n myenv --file package-list.txt
gives me this error:
Solving environment: ...working... failed
PackagesNotFoundError: The following packages are not available from current channels:
- markdown==2.6.11=py_0
...
... then try to use conda env export
According to this discussion execute the following command on your source machine:
source activate yourEnvironment
conda env export --no-builds > file.txt
On the target machine execute:
conda env create --file /path/to/file.txt
The file generated by conda env export
looks a bit different, but it contains pip packages as well:
name: yourEnvironment
channels:
- conda-forge
- defaults
dependencies:
- absl-py=0.5.0
...
- pip:
- astroid==2.0.4
...
add a comment |
Your Answer
StackExchange.ifUsing("editor", function () {
StackExchange.using("externalEditor", function () {
StackExchange.using("snippets", function () {
StackExchange.snippets.init();
});
});
}, "code-snippets");
StackExchange.ready(function() {
var channelOptions = {
tags: "".split(" "),
id: "1"
};
initTagRenderer("".split(" "), "".split(" "), channelOptions);
StackExchange.using("externalEditor", function() {
// Have to fire editor after snippets, if snippets enabled
if (StackExchange.settings.snippets.snippetsEnabled) {
StackExchange.using("snippets", function() {
createEditor();
});
}
else {
createEditor();
}
});
function createEditor() {
StackExchange.prepareEditor({
heartbeatType: 'answer',
autoActivateHeartbeat: false,
convertImagesToLinks: true,
noModals: true,
showLowRepImageUploadWarning: true,
reputationToPostImages: 10,
bindNavPrevention: true,
postfix: "",
imageUploader: {
brandingHtml: "Powered by u003ca class="icon-imgur-white" href="https://imgur.com/"u003eu003c/au003e",
contentPolicyHtml: "User contributions licensed under u003ca href="https://creativecommons.org/licenses/by-sa/3.0/"u003ecc by-sa 3.0 with attribution requiredu003c/au003e u003ca href="https://stackoverflow.com/legal/content-policy"u003e(content policy)u003c/au003e",
allowUrls: true
},
onDemand: true,
discardSelector: ".discard-answer"
,immediatelyShowMarkdownHelp:true
});
}
});
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f45864595%2fhow-to-transfer-anaconda-env-installed-on-one-machine-to-another-both-with-ubu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
2 Answers
2
active
oldest
votes
2 Answers
2
active
oldest
votes
active
oldest
votes
active
oldest
votes
From the very end of this documentation page:
Save packages for future use:
conda list --export > package-list.txt
Reinstall packages from an export file:
conda create -n myenv --file package-list.txt
add a comment |
From the very end of this documentation page:
Save packages for future use:
conda list --export > package-list.txt
Reinstall packages from an export file:
conda create -n myenv --file package-list.txt
add a comment |
From the very end of this documentation page:
Save packages for future use:
conda list --export > package-list.txt
Reinstall packages from an export file:
conda create -n myenv --file package-list.txt
From the very end of this documentation page:
Save packages for future use:
conda list --export > package-list.txt
Reinstall packages from an export file:
conda create -n myenv --file package-list.txt
answered Sep 12 '18 at 0:35
MiladioussMiladiouss
573615
573615
add a comment |
add a comment |
If conda list --export
failes like this ...
Executing conda list --export > package-list.txt
creates a file which looks like this:
# This file may be used to create an environment using:
# $ conda create --name <env> --file <this file>
# platform: win-64
_tflow_1100_select=0.0.1=gpu
absl-py=0.5.0=py_0
astor=0.7.1=py_0
...
But creating a new environment by executing conda create -n myenv --file package-list.txt
gives me this error:
Solving environment: ...working... failed
PackagesNotFoundError: The following packages are not available from current channels:
- markdown==2.6.11=py_0
...
... then try to use conda env export
According to this discussion execute the following command on your source machine:
source activate yourEnvironment
conda env export --no-builds > file.txt
On the target machine execute:
conda env create --file /path/to/file.txt
The file generated by conda env export
looks a bit different, but it contains pip packages as well:
name: yourEnvironment
channels:
- conda-forge
- defaults
dependencies:
- absl-py=0.5.0
...
- pip:
- astroid==2.0.4
...
add a comment |
If conda list --export
failes like this ...
Executing conda list --export > package-list.txt
creates a file which looks like this:
# This file may be used to create an environment using:
# $ conda create --name <env> --file <this file>
# platform: win-64
_tflow_1100_select=0.0.1=gpu
absl-py=0.5.0=py_0
astor=0.7.1=py_0
...
But creating a new environment by executing conda create -n myenv --file package-list.txt
gives me this error:
Solving environment: ...working... failed
PackagesNotFoundError: The following packages are not available from current channels:
- markdown==2.6.11=py_0
...
... then try to use conda env export
According to this discussion execute the following command on your source machine:
source activate yourEnvironment
conda env export --no-builds > file.txt
On the target machine execute:
conda env create --file /path/to/file.txt
The file generated by conda env export
looks a bit different, but it contains pip packages as well:
name: yourEnvironment
channels:
- conda-forge
- defaults
dependencies:
- absl-py=0.5.0
...
- pip:
- astroid==2.0.4
...
add a comment |
If conda list --export
failes like this ...
Executing conda list --export > package-list.txt
creates a file which looks like this:
# This file may be used to create an environment using:
# $ conda create --name <env> --file <this file>
# platform: win-64
_tflow_1100_select=0.0.1=gpu
absl-py=0.5.0=py_0
astor=0.7.1=py_0
...
But creating a new environment by executing conda create -n myenv --file package-list.txt
gives me this error:
Solving environment: ...working... failed
PackagesNotFoundError: The following packages are not available from current channels:
- markdown==2.6.11=py_0
...
... then try to use conda env export
According to this discussion execute the following command on your source machine:
source activate yourEnvironment
conda env export --no-builds > file.txt
On the target machine execute:
conda env create --file /path/to/file.txt
The file generated by conda env export
looks a bit different, but it contains pip packages as well:
name: yourEnvironment
channels:
- conda-forge
- defaults
dependencies:
- absl-py=0.5.0
...
- pip:
- astroid==2.0.4
...
If conda list --export
failes like this ...
Executing conda list --export > package-list.txt
creates a file which looks like this:
# This file may be used to create an environment using:
# $ conda create --name <env> --file <this file>
# platform: win-64
_tflow_1100_select=0.0.1=gpu
absl-py=0.5.0=py_0
astor=0.7.1=py_0
...
But creating a new environment by executing conda create -n myenv --file package-list.txt
gives me this error:
Solving environment: ...working... failed
PackagesNotFoundError: The following packages are not available from current channels:
- markdown==2.6.11=py_0
...
... then try to use conda env export
According to this discussion execute the following command on your source machine:
source activate yourEnvironment
conda env export --no-builds > file.txt
On the target machine execute:
conda env create --file /path/to/file.txt
The file generated by conda env export
looks a bit different, but it contains pip packages as well:
name: yourEnvironment
channels:
- conda-forge
- defaults
dependencies:
- absl-py=0.5.0
...
- pip:
- astroid==2.0.4
...
answered Nov 19 '18 at 23:21
John JohnsonJohn Johnson
141110
141110
add a comment |
add a comment |
Thanks for contributing an answer to Stack Overflow!
- Please be sure to answer the question. Provide details and share your research!
But avoid …
- Asking for help, clarification, or responding to other answers.
- Making statements based on opinion; back them up with references or personal experience.
To learn more, see our tips on writing great answers.
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
StackExchange.ready(
function () {
StackExchange.openid.initPostLogin('.new-post-login', 'https%3a%2f%2fstackoverflow.com%2fquestions%2f45864595%2fhow-to-transfer-anaconda-env-installed-on-one-machine-to-another-both-with-ubu%23new-answer', 'question_page');
}
);
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Sign up or log in
StackExchange.ready(function () {
StackExchange.helpers.onClickDraftSave('#login-link');
});
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Sign up using Google
Sign up using Facebook
Sign up using Email and Password
Post as a guest
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
Required, but never shown
You should be able to do
conda list --export > requirements.txt
and then on your new environment doconda create --name [env name] --file requirements.txt
– gobrewers14
Aug 24 '17 at 14:53
wouldn't that only work if the packages and libraries are out of the shelf and to be installed from pip?. by your method i will have the name list of packages. and in new env those packages will be installed from pip again. but the problem is i have custom built packages which had dependent configurations with each other
– Qaisar Rajput
Aug 24 '17 at 15:00