Settings are not persisted between restarts

[donfrigo]

Hello,

I am using the octoprint-docker image with the default docker-compose file, which specifies a volume.

When starting octoprint with the command:
docker-compose up -d
it starts up normally and I am greeted with the setup.

If I stop it using:
docker-compose down,
it stops gracefully.

Upon restarting it again, I am greeted with the same setup that I have completed earlier and all my settings are lost. What am I doing wrong? Thanks!

[atom-b]

I submitted pull request #72 to fix this. It's a very simple change to docker-compose.yml that you can make yourself if you don't want to wait for it to be merged (assuming it is =) ).

If you have a config you want to keep then be sure to run a full octoprint backup before running docker-compose down.

After stopping your container you'll need to delete the existing octoprint volume. Run docker volume rm octoprint-docker_octoprint to do that. In case your volume isn't named that, run docker volume ls to find it; it should have octoprint in the name.

[LongLiveCHIEF]

this is actually due to a bug in the current build that I'll be fixing. For now, the indicated workaround will work. I'm not going to accept the PR, because the final build image when the bug is fixed actually symlinks /home/octoprint to /octoprint.