[After entering the command “./webodm.sh start” into Git Bash, I get the output below.
Checking for docker… OK
Checking for git… OK
Checking for docker-compose… OK
Starting WebODM…
Using the following environment:
Host: localhost
Port: 8000
Media directory: appmedia
SSL: NO
SSL key:
SSL certificate:
SSL insecure port redirect: 80
Celery Broker: redis://broker
Default Nodes: 1
Make sure to issue a ./webodm.sh down if you decide to change the environment.
docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml start || docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml up --scale node-odm=1
Starting node-odm … failed
Starting broker … failed
Starting db … failed
Starting worker … failed
Starting webapp … failed
No containers to start
Pulling node-odm (opendronemap/nodeodm:)…
latest: Pulling from opendronemap/nodeodm]
What should be the expected behavior?
[I expect WebODM to be accessible in my browser and for a container to be visible on Docker Desktop]
How can we reproduce this? (What steps did you do to trigger the problem? What parameters are you using for processing? Please include multiple screenshots of the problem! If possible please include a copy of your dataset uploaded on Google Drive or Dropbox. Be detailed)
[ Unfortunately, I’m not sure. My Docker Desktop settings are below and I’ve copied the GIT Bash output. If any other information would be useful, please let me know.
Resources
Advanced
CPUs: 5
So, I recently tried to run ODM from the command prompt window and was able to get it working. I’m not sure if that helps diagnose what’s wrong with my WebODM issue, but I think it suggests that Docker isn’t the problem?
[email protected] MINGW64 ~/webodm (master)
$ ./webodm.sh start
Checking for docker… OK
Checking for git… OK
Checking for docker-compose… OK
Starting WebODM…
Using the following environment:
Host: localhost
Port: 8000
Media directory: appmedia
SSL: NO
SSL key:
SSL certificate:
SSL insecure port redirect: 80
Celery Broker: redis://broker
Default Nodes: 1
Make sure to issue a ./webodm.sh down if you decide to change the environment.
docker-compose -f docker-compose.yml -f docker-compose.nodeodm.yml start || docker-compose -f docker-compose.ym l -f docker-compose.nodeodm.yml up --scale node-odm=1
Starting db … failed
Starting node-odm … failed
Starting broker … failed
Starting worker … failed
Starting webapp … failed
No containers to start
Pulling broker (redis:)…
latest: Pulling from library/redis
Digest: sha256:800f2587bf3376cb01e6307afe599ddce9439deafbd4fb8562829da96085c9c5
Status: Downloaded newer image for redis:latest
Pulling node-odm (opendronemap/nodeodm:)…
latest: Pulling from opendronemap/nodeodm
I’m really impressed with the software and want to learn how to use effectively.
I really don’t understand how to use the software, properly.
I’ve been able to manage some photogrammetry reduction in WebODM, but it doesn’t seem to process anything more than a few images. That isn’t really what it’s capable of.
I had tried to run ODM in Windows and Ubuntu utilising python, docker and git. I really am still trying to get my head around the ‘container’.
I really haven’t used any UNIX command driven software since 1998, when I started to learn surveying.
Can you help me understand?
docker opens on a platform.
The odm image is installed in a container.
Python is installed in the container.
odm runs in the container with Python.
ODM runs process?
I will work this out, eventually.
I think I’ll try piecing the WebODM process flows together and tweak the variables for each stage depending on the dataset and hopefully getting the software to work.
So far, I haven’t seen a solution other than to run it from the console instead of WebODM, but it’s a lot less intuitive. I only did it twice right after I posted this and then got distracted and haven’t tried since. Any luck here?
Solution: I waited several months, deleted all of the cloned files and re-cloned them from git GUI. Then I opened git Bash and tried the command one more time. I got the same “no containers to start” error and just waited for a long time and then all of the sudden everything started running. Looks like it might be that my computer is a little under specs and it just takes a lot longer to get things done
