Closed ipetrovits closed 1 year ago
Of course changing Volume did the trick, but I afraid this shouldn't behave like this:
volumes:
- ./data:/home/app/.local/share/spoolman/
Sorry to hear that you lost your data, but that's just how docker works. You decided to change the example config that I have provided, that's on you. I don't think I can make any changes to prevent this from happening again.
ohh crap..
I forgot that I had to modify the compose file multiple times, because it did not run with version 3.8 in general.. (For some reason the docker-compose I pulled having trouble with that version. I'm running mainsail customized PI image btw..)
Now I feel totally stupid, i don't really remember when I deviated this much from the original config (I rewrote compose file a few times), I guess I just got so excited by the fact it started working, I forgot to check db file.
Thanks for your comment, sorry for being a dumbass.
Hi, first od all this is a really Great project!!
I'm using Spoolman for around a month now, and didn't realized that the spoolman.db was not created inside /data folder. Unfortunately all of my data was gone when I pulled the new docker image. Started investigating, and found this in the startup:
And indeed, when I log into the container, the .db file is there, but this is not a volume specified on my pi. My docker-compose file is:
Is this normal, or what did I miss? Thanks!