nova vigil
The short version -
I need to know what file(s) to copy over from the old host to the new one to preserve my data and settings.
The long version -
I have had Authentik running in it's own environment in an LXC container in Proxmox with very little issue, but am planning on migrating away from Promxox so this means that I will be setting Authentik up on a new host (a.k.a. non-LXC container). What is the best solution to do this so I can preserve my settings across the board?
keen mica
my first instinct would be to see which mounting points the docker compose container uses (though I'm sure there's a better answer). That way you can find out what data you should persist and copy over even though you're not using docker compose
nova vigil
Thanks, I tried that but it just resets the install and I am back to squaare one with setup. I also tried copying the /var/lib/docker/container directory into the ones created by the docke compose installation and it did the same thing with that copied data.
nova vigil
Any other ideas anyone?
cobalt mango
im not sure how your set up is since i dont user promax but your data doesnt go into a database like progres?
nova vigil
It's running in an LXC in Portainer and I don't want to use the LXC anymore. I was planning on moving away from Proxmox to a different server. I have full root and SSH on both machines so can grab whatever is needed. But I am using the default docker-compose from Authentik's site so mapping is pretty basic.
nova vigil
SOLVED I found the postgres database mapped to /var/lib/docker/volumes/root_database folder: (As was mapped by their docker-compose.yml). It was prefixed with root as I installed the compose from the root directory on the server dedicated for this.
I was able to copy the entire directory to a mapped folder on the new system and remap the compose defined directories to that custom directory I defined.
The initial problem was I could not get the full system copied and transferred including my user database and settings as well as the media files, forcing it to be defaulted. The cause behind this was I didn't copy the docker volumes directory basically which contained the postgres database.