Kallb123

It works! The data showed up (an hour late), so I removed the container and ran it again. The same data is still visible. Thank you for your help koyaanisqatsi, your idea of creating a starter database is spot on!! The timezone issue doesn't seem to be fixed even after editing that php file

I might have managed it... though I can't see any data yet, maybe it'll show up in an hour (my timezone offset). I firstly ran: sudo docker run --name cacti -d -p 9123:80 -p 161:161 --restart always -e TZ=Europe/London \ -v /home/x/cacti/cacti:/data/cacti -v /home/x/cacti/mysql:/data/mysql quantumobject/docker-cacti then access the container terminal with sudo docker exec -it cacti bash I gave it ~10 minutes to start and gather some data. I then transferred all the files: rsync -a /var/lib/mysql/* /data/mysql/ rsync -a /opt/cacti/* /data/cacti/ I then removed the container and started it with the new volumes: sudo docker run --name cacti -d -p 9123:80 -p 161:161 --restart always -e TZ=Europe/London \ -v /home/x/cacti/cacti:/opt/cacti -v /home/x/cacti/mysql:/var/lib/mysql quantumobject/docker-cacti It seems to have booted and there's no errors. But I'll have to wait for data to show up. You could do the same with more volumes for maximum customisability I suppose. I haven't tested multiple restarts, I'll wait for data first. EDIT: Folder ownership seems to have been messed up, but the files seem ok. Too early to tell whether the permissions are going to screw it up.

That's odd about the timezone. I actually found that my host was on UTC rather than London time, so that might help my situation. Haven't tested yet. I'm struggling with persistence too. I found that /var/lib/mysql and /opt/cacti are where the configs are stored and if they can be passed as a volume then that would work. However, when I pass them through as volumes the container stops working. The following command, in my eyes, should start the container with persisted volumes: docker run --name cacti -d -p 9123:80 -p 161:161 --restart always -e TZ=Europe/London \ -v /home/x/cacti/cacti:/opt/cacti -v /home/x/cacti/mysql:/var/lib/mysql quantumobject/docker-cacti I must be missing something about the writing of the volumes as it just stops working with this change. I found https://hub.docker.com/r/idle/cacti-1-minute/ which should have persistence, but this also fails to start up. Note that the cacti config here is said to be /var/lib/cacti. Let us know if you figure out persistence. I'll update you too if anything works for me.

Thank you for updating and posting this!! I'm trying to get this same docker running (quantumobject/docker-cacti) and I have the same timezone issue. I'm not within unRaid, just bare Ubuntu. This was the only result that showed up though. Could you explain how you fixed the timezone issue? I'm unsure how to put putenv('TZ=America/Los_Angeles'); into the docker system (persistently). I've also been wondering how this system copes with a reboot. I've not specified any persistent volumes, so do all the stats wipe when the container restarts?