ENOTDIR: not a directory

Mm, is node-dir a normal filesystem or a network drive? Is this Windows?

Yes it’s Docker in windows and the three folders are all located in documents folder

./webodm/webodm.sh start --media-dir "C:/Users/username/Documents/WebODM/Data" --db-dir "C:/Users/username/Documents/WebODM/DB" --node-dir "C:/Users/username/Documents/WebODM/Temp"

I didn't mention error appears 2-3 seconds after images are sent to node, and log file is empty

Is docker configured to use WSL2 ?

I think so, how can I double check?

I use .wslconfig file to set memory size etc

Somewhere in the docker app it should say so; I don't use Windows much, but I remember years ago I encountered issues to mounting volumes on Windows while using docker. There's some synchronization problems which I don't know if they have fixed since. My suggestion would be to use the native version of WebODM on Windows to avoid these kind of problems.

It was in my plan to start using the native version, and I was able to get up and running for remote access (the pc is headless), but with a test run it took about 50% much time than the Docker version

Maybe it was something messed up trying to start it on the right port

maybe; if performance is really critical, consider using Linux + docker, which should be the fastest

well it's not so critical for now but I noticed a 5 hours time vs a 3 hours time for the same set with the same preset, it sounded strange since with Docker I don't allocate the full ram but only 24/32 GB

After a full machine reboot it went a little further: 4ebfbc66-5595-4e92-9c54-b5605bf7b403 not found

I created a new project and from the new project it seems to be running. May this be because the old project folder was created when --node-dir was not specified and that broke some paths?

The task completed, after running another new task both on the same project folder or a new project folder it failed with same error as before, I will do some random tests to see if I can figure it out

Hello, I tried installing WebODM from scratch on another PC for testing purposes, and starting with --media-dir, --node-dir and --db-dir fails. Particularly the problem is with the --db-dir argument, terminal spits out lots of errors, the most recurring is "Postgres is unavailable - sleeping" and loops forever. Starting without --db-dir option works as expected

I noticed that in the installation procedure in the website to save space no mention is done to --db-dir but only to the other two arguments, so maybe this is not relevant for space saving since the big files are stored in the other two folders?

I noticed that the db folder in my main installation is more or less 70 MB, if no big files are saved here during process I think I can disregard the --db-dir, since it doesn't impact on space consumption

P.S. as you may have guessed, I'm not familiar with what is stored in the db directory, so this may be a dumb question 🙂

I tried a test installation in a Mac and that worked with all --media-dir --db-dir and --node-dir, while I tried on another instance in Windows and --node-dir makes the software crash at the second task (first one completes correctly)

Seems like a WSL issue (wsl --shutdown lets a single task to run, the following stops with same error); I wanna try a fresh Windows installation on a new machine to ensure it's not something I messed up during multiple tests I did in last months

Maybe if it turns out that the issue appears on a really fresh install of webodm with docker I can open an issue

BTW I figured out the error I was referring to in last message (Postgres is unavailable - sleeping), it was due to windows firewall being too aggressive (I hate it)