Jellyseerr doesn't retain config about jellyseerr HOT 7 CLOSED

Ok, I have no idea why, but reloading the original docker-compose file now works fine. I have not changed anything yet now if I restart the container it retains the config.

from jellyseerr.

Thank you for your help. The project is amazing btw

from jellyseerr.

That is probably because permission issue. Jellyseerr is unable to write the configs to the folder that is mapped so it is unable to retain the config.

Please ensure the config folder has the right permissions.

Also side note: for restarts it's better to use docker restart jellyseerr

from jellyseerr.

I don't think that's the problem because if I open the file settings.json inside the config folder, I can see that Jellyseerr wrote into it before. The config folder belongs to root and has rw permission.

Thanks for the advice btw.

from jellyseerr.

Is there anything in the logs?
Also to test could you try mapping the config folder to a docker volume? You can do this by

docker create volume config

And in docker-compose
- config:/app/config

Also you just said the config folder belongs to root and not username. Could you clown it to username? Because to my understanding of how docker works, when you don't specify the docker user, it will automatically use the user that created the container so if username created it, but the config folder is owned by root it will not be able to read a second time.

from jellyseerr.

I did that, but now when I open the webpage I get this warning : The /app/config volume mount was not configured properly. All data will be cleared when the container is stopped or restarted.
This doesn't appear when I create the container with the docker-compose file that I posted above

from jellyseerr.

I did that, but now when I open the webpage I get this warning : The /app/config volume mount was not configured properly. All data will be cleared when the container is stopped or restarted.
This doesn't appear when I create the container with the docker-compose file that I posted above

For future reference, though that appears as long as the volume is retained in your device the configs would remain. I use volumes for when testing though I do not recommend that to run as production

Anyways, glad you solved it!

from jellyseerr.