I have installed WebODM successfully using Docker on my Windows 7 machine, but I have QNAP NAS that would be perfect for running the docker version instead. My NAS has GUI based app called Container Station that allows quick installation of pre-built docker containers. I found the following container on the Docker Hub: Docker
I ran the installer and all seems to be functioning correctly but I have no idea where to go from here? Does anyone have any experience running WebODM on a QNAP NAS and help me sort out how to run enough commands to sort out the IP address of the web server running in the container so I can get to the WebODM GUI?
I don’t have a QNAP NAS, but I would guess that they’re not a good host for ODM. Typically those off-the-shelf NAS systems are delivered with the bare minimum specs required to manage disks, run a web UI and deliver SMB/NFS to the network. Even tiny surveys in ODM will be using about 6-8GB RAM.
Sorry for the bad news, but it’s probably best you hear it now before spending hours getting it going only to find that it’s not a suitable platform. However, if you are keen to get it running, I’d love to see how a survey from a NAS would look!
Thanks for the input. The NAS I have is configurable with 64 GB of ram. If I can do this proof of concept I will purchase the memory and install it.
Holy smoke, those things have come a long way! Yeah, that sounds like it’s worth a try then.
Try to figure out what operating system it’s running; hopefully it’s Linux. Try to figure out if ODM is listening on the the correct ports. Use netstat if you have it, you’re looking for port 3000:
[email protected]:~# netstat -tapn | grep LIST | grep 3000
tcp6 0 0 :::3000 :::* LISTEN 1748/node
If you don’t have netstat, try to telnet to the port:
[email protected]:~# telnet 127.0.0.1 3000
Connected to 127.0.0.1.
Escape character is '^]'.
If that works, then you’ll probably want to try to figure out the IP; use
ip addr or
ifconfig. Then telnet to that IP to make sure ODM is listening on an IP address that you can reach from your machine. If that’s listening and you can’t reach it via your browser, your NAS may be running a firewall - there are several, but the most likely is
iptables -L -n and see what you get.
Let us know how you get on!