Closed zahid990170 closed 4 months ago
Hello,
I don't know whether you managed to solve this...I think the issue you are facing is because of line 1 in the run_container.sh
script, docker rm -f bundlesdf
. docker rm
deletes a container. But the first time you run run_container.sh
, no container instance with the name bundlesdf
is already running, therefore this error occurs. Try commenting out that line...
Actually my first answer was incomplete....the error response from daemon
occurs because of what I mentioned, however the bash script continues to execute, so line 1 is not the main issue here... The reason the container fails to run is probably due to issues with X11 forwarding. You could check the replies to a relevant question here
thanks @athnzc, the main issue regarding running docker container is resolved. However, I am on a local machine and ssh to the GPU where bundle repo is cloned. For enabling X forwarding, I should do it while I am inside the docker container.
@zahid990170 Sorry if I misunderstood, so the main issue was solved by enabling X Forwarding while inside the container?
thanks @athnzc, the main issue regarding running docker container is resolved. However, I am on a local machine and ssh to the GPU where bundle repo is cloned. For enabling X forwarding, I should do it while I am inside the docker container.
you can rename the docker image from nvcr.io/nvidian/bundlesdf
to bundlesdf
with docker tag
Hi,
I recently started trying setup BundleSDF by following the instructions given in the readMe. After having built the docker image (which took a long time (> 1 h 30 minutes on GeForce RTX 2070 SUPER) using the following command:
docker build --network host -t nvcr.io/nvidian/bundlesdf .
Is this the tag for the docker image:nvcr.io/nvidian/bundlesdf
?when I issue this command:
sudo bash run_container.sh
I get an error
was the docker image not built?
thanks,