Docker container size?

Hi there. I have been a proud member of this forum for about 30 minutes, and could use some help, which I hope is simple…

System: Dell R610, 64GB RAM / ~ 1+TB available
Fedora 34 Server

at some point during processing: i get this:

ERROR] Uh oh! Processing stopped because of strange values in the reconstruction. This is often a sign that the input data has some issues or the software cannot deal with it. Have you followed best practices for data acquisition? See https://docs.opendronemap.org/flying.html
Cannot write log.json: [Errno 28] No space left on device: ‘/var/www/data/e7768450-1edc-4bea-8a6c-4fb18f977eda/log.json’

looking at the docker container sizes, it appears as though it happens when nodeodm gets to about 10GB?

[jeff@fedora webodm]$ docker ps -s
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES SIZE
fac67be0448f opendronemap/webodm_webapp “/bin/bash -c 'chmod…” 39 minutes ago Up 36 minutes 0.0.0.0:8000->8000/tcp, :::8000->8000/tcp webapp 532kB (virtual 1.74GB)
9cc4b0a01f11 opendronemap/webodm_webapp “/bin/bash -c '/webo…” 39 minutes ago Up 36 minutes worker 67.1kB (virtual 1.74GB)
e80a11a8fa3d redis “docker-entrypoint.s…” 39 minutes ago Up 36 minutes 6379/tcp broker 0B (virtual 105MB)
00a50d28d629 opendronemap/webodm_db “docker-entrypoint.s…” 39 minutes ago Up 36 minutes 0.0.0.0:49166->5432/tcp, :::49166->5432/tcp db 48B (virtual 695MB)
18dc3d834ea8 opendronemap/nodeodm “/usr/bin/node /var/…” 39 minutes ago Up 36 minutes 0.0.0.0:49165->3000/tcp, :::49165->3000/tcp webodm_node-odm_1 3.35GB (virtual 5.05GB)

when this occurs, the terminal output switches to:

node-odm_1 | info: About to run: /code/run.sh --pc-quality high --dsm --split 50 --split-overlap 20 --pc-ept --cog --project-path /var/www/data e7768450-1edc-4bea-8a6c-4fb18f977eda
broker | 1:M 05 Oct 2021 23:12:18.020 * 100 changes in 300 seconds. Saving…
broker | 1:M 05 Oct 2021 23:12:18.021 * Background saving started by pid 20
broker | 20:C 05 Oct 2021 23:12:18.025 * DB saved on disk
broker | 20:C 05 Oct 2021 23:12:18.026 * RDB: 0 MB of memory used by copy-on-write
broker | 1:M 05 Oct 2021 23:12:18.121 * Background saving terminated with success
broker | 1:M 05 Oct 2021 23:17:19.047 * 100 changes in 300 seconds. Saving…
broker | 1:M 05 Oct 2021 23:17:19.048 * Background saving started by pid 21
broker | 21:C 05 Oct 2021 23:17:19.052 * DB saved on disk
broker | 21:C 05 Oct 2021 23:17:19.053 * RDB: 0 MB of memory used by copy-on-write
broker | 1:M 05 Oct 2021 23:17:19.149 * Background saving terminated with success
broker | 1:M 05 Oct 2021 23:22:20.097 * 100 changes in 300 seconds. Saving…
broker | 1:M 05 Oct 2021 23:22:20.097 * Background saving started by pid 22
broker | 22:C 05 Oct 2021 23:22:20.100 * DB saved on disk
broker | 22:C 05 Oct 2021 23:22:20.100 * RDB: 0 MB of memory used by copy-on-write
broker | 1:M 05 Oct 2021 23:22:20.197 * Background saving terminated with success
broker | 1:M 05 Oct 2021 23:27:21.006 * 100 changes in 300 seconds. Saving…
broker | 1:M 05 Oct 2021 23:27:21.007 * Background saving started by pid 23
broker | 23:C 05 Oct 2021 23:27:21.012 * DB saved on disk
broker | 23:C 05 Oct 2021 23:27:21.013 * RDB: 0 MB of memory used by copy-on-write
broker | 1:M 05 Oct 2021 23:27:21.107 * Background saving terminated with success
db | LOG: could not open temporary statistics file “pg_stat_tmp/global.tmp”: No space left on device

I am hoping this is a simple flag for docker (similar to the control i seen my mac) for controlling resources?

Thanks for any guidance in this.

Regards,
Jeff

1 Like

Could you give this a go?

I went through a variety of these (and others) over the past couple of days. I suspect that my “loyalty” to fedora was complicating things…folks seem to prefer UBUNTU?

So… as it turns out, it was the file location being attached to the root, and finally, right before jumping onto the UBUNTU bandwagon, I ran across lvresize, added 150G to root and all my problems evaporated.

I don’t know of anyone else runs into this, but here is a link to the guthub page that solved all my problems.

Thanks, Saijin_Naib, for the welcome and pointers. While Bobcares didn’t help fix my issue, it certainly did help me better understand the structure of things.

Best,
Jeff

3 Likes

Sorry I missed the mark, and glad you got sorted!

Thanks for the link. Should come in handy if others get stuck as well.

Yeah, I think people like Debian/Ubuntu due to how large the community is. Nearly every Q/A or FAQ assumes usage of them, so it makes it great for self-help.

I like things difficult, so I use Alpine :rofl:

1 Like