Organizr on docker, loose Homepage settings after restart

After the container for organizer restarts I loose all the Homepage settings. The rest of the settings remain such as additional Tabs, etc… I even tried to restore a backup of organizer using the built in backup function, and this seems to not restore the homepage settings either. thanks,

Our :crystal_ball: is broken so you’ll need to provide more information such as Host OS / how you deployed the container with commands etc.


was hoping it might have been something you have come across below,

command is below,

docker create
-e PUID=1000
-e PGID=1000
-e TZ=Europe/London>
-p 9983:80
-v /docker/organizr/config:/config
–restart unless-stopped \

Host OS is Alpine Linux v3.9 with Kernel 4.19.34-0-vanilla and Docker version 18.09.1-ce (API: 1.39)

Host is a VM within FreeNAS bhyve,


Anything in the docker logs when starting the container up? I’m going to assume /docker/ folder ir a remote mount?

Yes /docker is a NFS mounted share. Permissions looks ok to me with UID 1000 and GID 1000 set to R/W.

Logs below from container,

User uid: 1000,
User gid: 1000,
[cont-init.d] 10-adduser: exited 0.,
[cont-init.d] 20-config: executing… ,
[cont-init.d] 20-config: exited 0.,
[cont-init.d] 30-keygen: executing… ,
using keys found in /config/keys,
[cont-init.d] 30-keygen: exited 0.,
[cont-init.d] 50-config: executing… ,
[cont-init.d] 50-config: exited 0.,
[cont-init.d] 99-custom-scripts: executing… ,
[custom-init] no custom scripts found exiting…,
[cont-init.d] 99-custom-scripts: exited 0.,
[cont-init.d] done.,
[services.d] starting services,
[services.d] done.,

We don’t recommend putting /config on remote mounts. Put it on the local FS of the VM and see if you still have the same issue.

I think its because Organizr is using config file /var/www/html/config/config.php. When i make changes to the homepage only this file is updated, which isnt in a persistent volume.

Will create a binding in docker, and try again

we symlink that file

It’s likely not being created in your persistent volume because of the NFS mount.

ok i think i got it now after a few attempts, and seems to remain now over restarts.