I can't call dpkg -i within a shell script [on hold]
up vote
0
down vote
favorite
I am on a Google cloud machine and I want to install CUDA.
When I type in the following commands successively, all works fine:
wget https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64-deb
sudo dpkg -i cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64.deb
But when I embedd the previous code in an install.sh
file like the following
#!/bin/sh
wget https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64-deb
sudo dpkg -i cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64.deb
and I call the file like this:
source ./install.sh
I get the following error
dpkg: error: cannot access archive 'cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64.deb': No such file or directory
I am 100% sure that I am located where the file is before calling the script. I am using Ubuntu 18.1
bash dpkg cuda
New contributor
put on hold as off-topic by steeldriver, N0rbert, karel, Eric Carvalho, muru Nov 28 at 1:24
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – steeldriver, N0rbert, karel, Eric Carvalho, muru
If this question can be reworded to fit the rules in the help center, please edit the question.
add a comment |
up vote
0
down vote
favorite
I am on a Google cloud machine and I want to install CUDA.
When I type in the following commands successively, all works fine:
wget https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64-deb
sudo dpkg -i cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64.deb
But when I embedd the previous code in an install.sh
file like the following
#!/bin/sh
wget https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64-deb
sudo dpkg -i cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64.deb
and I call the file like this:
source ./install.sh
I get the following error
dpkg: error: cannot access archive 'cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64.deb': No such file or directory
I am 100% sure that I am located where the file is before calling the script. I am using Ubuntu 18.1
bash dpkg cuda
New contributor
put on hold as off-topic by steeldriver, N0rbert, karel, Eric Carvalho, muru Nov 28 at 1:24
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – steeldriver, N0rbert, karel, Eric Carvalho, muru
If this question can be reworded to fit the rules in the help center, please edit the question.
3
Does the file name end in.deb
, or-deb
?
– steeldriver
Nov 25 at 14:55
It was a-deb
. A million thanks, issue fixed. It is just like when you spend hours looking for a needle in a haystack.
– Marouen
Nov 25 at 14:58
add a comment |
up vote
0
down vote
favorite
up vote
0
down vote
favorite
I am on a Google cloud machine and I want to install CUDA.
When I type in the following commands successively, all works fine:
wget https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64-deb
sudo dpkg -i cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64.deb
But when I embedd the previous code in an install.sh
file like the following
#!/bin/sh
wget https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64-deb
sudo dpkg -i cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64.deb
and I call the file like this:
source ./install.sh
I get the following error
dpkg: error: cannot access archive 'cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64.deb': No such file or directory
I am 100% sure that I am located where the file is before calling the script. I am using Ubuntu 18.1
bash dpkg cuda
New contributor
I am on a Google cloud machine and I want to install CUDA.
When I type in the following commands successively, all works fine:
wget https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64-deb
sudo dpkg -i cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64.deb
But when I embedd the previous code in an install.sh
file like the following
#!/bin/sh
wget https://developer.nvidia.com/compute/cuda/8.0/Prod2/local_installers/cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64-deb
sudo dpkg -i cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64.deb
and I call the file like this:
source ./install.sh
I get the following error
dpkg: error: cannot access archive 'cuda-repo-ubuntu1604-8-0-local-ga2_8.0.61-1_amd64.deb': No such file or directory
I am 100% sure that I am located where the file is before calling the script. I am using Ubuntu 18.1
bash dpkg cuda
bash dpkg cuda
New contributor
New contributor
New contributor
asked Nov 25 at 14:48
Marouen
1011
1011
New contributor
New contributor
put on hold as off-topic by steeldriver, N0rbert, karel, Eric Carvalho, muru Nov 28 at 1:24
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – steeldriver, N0rbert, karel, Eric Carvalho, muru
If this question can be reworded to fit the rules in the help center, please edit the question.
put on hold as off-topic by steeldriver, N0rbert, karel, Eric Carvalho, muru Nov 28 at 1:24
This question appears to be off-topic. The users who voted to close gave this specific reason:
- "This describes a problem that can't be reproduced, that seemingly went away on its own or was only relevant to a very specific period of time. It's off-topic as it's unlikely to help future readers." – steeldriver, N0rbert, karel, Eric Carvalho, muru
If this question can be reworded to fit the rules in the help center, please edit the question.
3
Does the file name end in.deb
, or-deb
?
– steeldriver
Nov 25 at 14:55
It was a-deb
. A million thanks, issue fixed. It is just like when you spend hours looking for a needle in a haystack.
– Marouen
Nov 25 at 14:58
add a comment |
3
Does the file name end in.deb
, or-deb
?
– steeldriver
Nov 25 at 14:55
It was a-deb
. A million thanks, issue fixed. It is just like when you spend hours looking for a needle in a haystack.
– Marouen
Nov 25 at 14:58
3
3
Does the file name end in
.deb
, or -deb
?– steeldriver
Nov 25 at 14:55
Does the file name end in
.deb
, or -deb
?– steeldriver
Nov 25 at 14:55
It was a
-deb
. A million thanks, issue fixed. It is just like when you spend hours looking for a needle in a haystack.– Marouen
Nov 25 at 14:58
It was a
-deb
. A million thanks, issue fixed. It is just like when you spend hours looking for a needle in a haystack.– Marouen
Nov 25 at 14:58
add a comment |
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
active
oldest
votes
3
Does the file name end in
.deb
, or-deb
?– steeldriver
Nov 25 at 14:55
It was a
-deb
. A million thanks, issue fixed. It is just like when you spend hours looking for a needle in a haystack.– Marouen
Nov 25 at 14:58