the container comes up fine.
I then stop the container and copy the database.yml with
Once I have everything that I think is need to recover from a container failure or to move to an updated container I stop the running container and remove it.
I would start up a new container with the same storage volumes as the previous container.
which I would get this error
I then copy the database.yml into the container while its trying to start up
and it seems to get stuck on the start of the EVM daemon.
I am wondering if there is another storage volume or some other config file needed to get a new container to come up with the configuration of a previous ManagIQ container? I would think this would be possible since persistent storage is an option with an openshift container. Am I backing up the correct directories and config files or going about this completely wrong?
I’ll take the liberty of bringing this up again. I tried to deploy ManageIQ in a container on a cluster swarm. I would like to be able to store the postgreSQL database and configuration on persistent volumes (vsphere volume). But I can’t, as soon as I try to map volumes, it doesn’t work anymore. Could you help me ?