Converting and Upgrading a Container

The document is marked as hidden as per Jinesh's Mail conversation.

Overview

A VM instance can be converted to run in a container to provide Administrators flexibility in their environments. 

However, items such as the keys.dat will need to be manually migrated from the instance over to the filestorage path of the new container. 

Alongside this, the properties from the Settings.xml must be turned into environment variables. 

When upgrading to a container, the instance must use a pre-existing database. Once the database is in use, other containers can be created using the same database.

This article will provide a brief overview of the needed items that will have to be migrated over to the container.

Migrating from a VM to a Container

1. To start, the properties from the Settings.xml need to be converted into environment variables. 
2. Then, copy the contents of the FileStorage of the non-container instance and paste them into the root folder of the container that will be used.
   
   

Upgrading Containers

When upgrading containerized instances of Decisions, the user will need to visit the Docker hub and retrieve the latest image of the Decisions container. 

Once retrieved, the user can apply the image to the container to have the environment upgraded. 

Similar steps to upgrading a Decisions environment should be followed, such as taking backups prior to upgrading the environment.

If upgrading a container to v8.5, the