[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
Using the following environment:
Media directory: appmedia
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.
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?
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