search

halajun / VDO_SLAM

VDO-SLAM: A Visual Dynamic Object-aware SLAM System
Other
734 stars 113 forks source link

unable to build using Dockerfile #51

Open Rong-Tao opened 1 year ago

Rong-Tao commented 1 year ago

I downloaded the Dockfile provided and try to build using: docker build -t vdo_slam .

And during the installation of https://github.com/opencv/opencv_contrib/archive/3.4.0.zip This error occurs: fatal error: opencv2/xfeatures2d/cuda.hpp: No such file or directory

I think this is the problem of openCV extra modules, could you give an updated Dockfile such that it can compile?

hu-xue commented 1 year ago

I have meet the same problem, and did u solve it?

Rong-Tao commented 1 year ago

Well, this is relate to Docker having different port, so I you are in China and need a VPN for some of the sources, the docker won't work for you. I didn't manage to solve the proxy for host machine, docker and my VPN setting which is an absolute mess and headache. I just installed it on my host machine instead. PAIN

hu-xue commented 1 year ago

Yes, I found that when I build the opencv_contrib lib from the source code, some packages could not been download. so I also try to install the enviroments in my own pc. not docker. And I also agree with the docker have some issue in China without a useful VPN. Thanks!

Rong-Tao commented 1 year ago

It is not really the issue of VPN only, but it is extremely painful to setup Docker proxy while setting up your own laptop's proxy and somehow connect them. Because for your host machine, the ip is 127.0.0.1 which is the same for docker. The docker machine think itself is 127.0.0.1 and your host machine is sth else, load of headache is ahead.

hu-xue commented 1 year ago

And I have a question, can I build a clean image of ubuntu16.04, then run this pure image on docker, and get into the image's terminal(but Idk the way to use the image's terminal.), to modify some settings to help the mirror machine install these packages?

Rong-Tao commented 1 year ago

yes, you can

  1. either setup proper proxy first on your host machine then your docker image
  2. You can pre download the source needed on your host machine (The missing files in the error msg) and include them in the build process, I think is like 20-30 ish