ManageIQ Docker with Persistent storage for configuration


When starting up the docker container with

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?


You have to save /var/www/miq/vmdb/GUID as well.

The thing that is missing in the docker image is starting postgresql:

systemctl start rh-postgresql95-postgresql
systemctl enable rh-postgresql95-postgresql


I copied off the GUID but it seems to get stuck starting up. I started the new container with the copied GUID.

It then seems to get stuck.

Am I going about this the wrong way? Is there a better way to backup the data and redeploy the manageiq docker container?


Has this been resolved, when trying to instantiate a container im getting:

[root@manageiqtest miq]# docker logs manageiq
[!!!] Failed to mount API filesystems, freezing.

- name: Pull manageIQ image
    name: manageiq
    detach: true
    image: manageiq/manageiq:fine-4
    state: started
    restart_policy: always
     - /opt/manageiq/data/db:/var/opt/rh/rh-postgresql95/lib/pgsql/data:Z
     - /opt/manageiq/data/certs:/var/www/miq/vmdb/certs:Z
     - /opt/manageiq/data/configs/GUID:/var/www/miq/vmdb/GUID:Z
    tty: true
    - 80:80
    - 443:443