pyORBSLAM2 icon indicating copy to clipboard operation
pyORBSLAM2 copied to clipboard

Pull Access denied for orbslam

Open joeliven opened this issue 7 years ago • 4 comments

Hi, thanks for setting up this repo, much appreciated!

Unfortunately though when I go to run sudo ./run.sh I get the following error:

Step 20/45 : RUN pip install numpy scipy
 ---> Using cache
 ---> 6f7309d230a7
Step 21/45 : ADD ./install/ssh-keys /root/.ssh
ADD failed: stat /var/lib/docker/tmp/docker-builder636356349/install/ssh-keys: no such file or directory
Removing older image...
Error: No such container: orbslam0
Running image...
Unable to find image 'orbslam:latest' locally
docker: Error response from daemon: pull access denied for orbslam, repository does not exist or may require 'docker login'.
See 'docker run --help'.
Template parsing error: template: :1: unexpected unclosed action in range
CONTAINER IP::
DOCKER IP::172.17.0.1
Error: No such container: orbslam0
DOCKER PUBLISHED PORT 22 -> ::
Host [172.17.0.1]: not found in /home/ubuntu/.ssh/known_hosts
Login password is: :
Bad port '[email protected]'

I've tried exporting SPASSWORD=source, but still doesn't seem to work.

Can you advise? Thanks!

joeliven avatar Mar 25 '18 18:03 joeliven

Hi, @schroeder-dewitt Same problem here, any hints?

syinari0123 avatar Jul 28 '18 09:07 syinari0123

same problem here also

djl11 avatar Aug 13 '18 22:08 djl11

The key error is here: ADD failed: stat /var/lib/docker/tmp/docker-builder636356349/install/ssh-keys: no such file or directory

A quick google search revealed that this is a common problem with the latest docker, on account of paths now needing to be relative as opposed to absolute, in the latest docker version. For example this and this issue.

I therefore simply removed nvidia-docker2 and reinstalled nvidia-docker1. I also manually created the directory install/ssh-keys manually inside the pyORBSLAM2 directory. This seems to have fixed this particular error for me.

djl11 avatar Aug 14 '18 14:08 djl11

This is because you don't have ssh-keys generated locally inside install/. A way to fix it is to generate the ssh-keys while building the Docker image. Change the block of commands inside Dockerfile to the following: # Set up ssh keys in order to be able to checkout TorrVision
RUN apt-get -y install openssh-client
RUN mkdir /root/.ssh
RUN cd /root/.ssh
RUN ssh-keygen -q -t rsa -N '' -f /ssh-keys
RUN mv -v ssh-keys* ~/.ssh
RUN chmod -R 600 /root/.ssh
RUN ssh-keyscan github.com > ~/.ssh/known_hosts

KolinGuo avatar May 01 '19 08:05 KolinGuo