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
  docker_container:
    name: manageiq
    hostname: manageiq.jungle.passage.nml.com
    detach: true
    image: manageiq/manageiq:fine-4
    state: started
    restart_policy: always
    volumes:
     - /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
    ports: 
    - 80:80
    - 443:443

Hi
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 ?

Here is the configuration of my stack

version: “3.3”

services:

manageiq:

image: manageiq/manageiq:ivanchuk-2

networks:

    - NET_OVE_TRAEFIK_PUBLIC

volumes:

  - VOL_VMW_MANAGEIQ_DATABASE:/var/lib/pgsql/data

  - VOL_VMW_MANAGEIQ_CONF:/var/www/miq/vmdb   

#ports:

#   - target: 443

#     published: 8443

#     mode: host    

deploy:

  replicas: 1

  placement:

    constraints:

     # - node.role == worker

     # - node.labels.dmz == no

      - node.hostname  == swawok002

  labels:

    - traefik.enable=true

    - traefik.http.routers.manageiq.entrypoints=websecure

    - traefik.http.routers.manageiq.tls=true

    - traefik.http.routers.manageiq.rule=Host(`manageiq.inf.prd.dck.coolcorp.priv`)

    - traefik.http.services.manageiq.loadbalancer.server.port=443

    - traefik.http.services.manageiq.loadbalancer.server.scheme=https

    #- "traefik.http.routers.manageiq.middlewares=authmanageiq"

    #- "traefik.http.middlewares.authmanageiq.basicauth.users=user:$$apr1$$q8eZFHjF$$Fvmkk//V6Btlaf2i/ju5n/"

    #- traefik.tcp.routers.manageiq.entrypoints=manageiq_input

    #- traefik.tcp.routers.manageiq.rule=HostSNI(`manageiq.inf.prd.dck.coolcorp.priv`)

    #- traefik.tcp.services.manageiq.loadbalancer.server.port=443        

networks:

NET_OVE_TRAEFIK_PUBLIC:

external: true

volumes:

VOL_VMW_MANAGEIQ_DATABASE:

  driver: vsphere

  driver_opts:

    size: 15Gb

VOL_VMW_MANAGEIQ_CONF:

  driver: vsphere

  driver_opts:

    size: 15Gb