The documented run command has -v sdods-data:/data in it. I dropped it to try the UI quickly, created a couple of things, and after a restart they were gone.
I assume that is the volume doing its job and I removed it. Before I put it back properly — what exactly lives in there, and can I point it at a directory instead of a named volume?
Accepted answer
Yes, that is exactly what happened. /data is where the platform database and run artifacts live, and --rm with no volume means the container filesystem goes away with the container.
A named volume is the simple form:
docker run --rm -p 8080:8080 -v sdods-data:/data ghcr.io/yarlisaisolutions/sdods-serverA host directory works the same way and is easier to back up or inspect:
docker run --rm -p 8080:8080 -v "$HOME/sdods-data":/data ghcr.io/yarlisaisolutions/sdods-serverDeployment shapes, including running it somewhere permanent, are in Guides → Hosting.
One gotcha with the host-directory form: the container writes as its own user, so on Linux you can end up with a directory you cannot read afterwards. A named volume sidesteps that entirely, which is probably why the docs lead with it.
Have a different question? Ask it.