Updating Siebel Cloud Manager with a New Container Image

You can update SCM with a new container image whenever one becomes available, such as when an updated version of SCM has become available.

To update SCM with a new container image

SSH into the SCM virtual machine instance.
Run the following command to find the current SCM container version which is active and note the image tag, that is, the current SCM version.
```
docker ps
```
Get the latest SCM application version from Oracle Marketplace (for example, CM_23.1.0).
Run the shell script for starting the SCM server with the latest application version as the input, as in these examples:
```
cd /home/opc
```
```
bash start_cmserver.sh CM_23.1.0
```
Verify the startup of the SCM application using the following command:
```
docker ps
```
Check the version of the running container in the image tag. It should match the input provided during the start shell.
After updating SCM with the new version, run the following command to get the new SCM features:
```
docker exec -it cloudmanager bash 
```
```
cd /home/opc
```
```
bash siebel-cloud-manager/scripts/cmapp/migration.sh
```
Choose one of the options presented by the migration.sh script. Run the script multiple times, as necessary, for all of the options you require.

Note: You might see GitLab merge conflict errors during migration. In such cases, fix the conflicts manually and try again.
File systems are also mounted in the SCM instance. Once the container is restarted, the existing mounts will be disconnected. In order to mount again, execute the following command:
```
sudo mount -t nfs {FILESYSTEM_HOST}:/{env-namespace}-siebfs{filesystem-index} /home/opc/siebel/{env_id}/{env-namespace}-siebfs{filesystem-index} -o nolock
```
All the information needed for the above command is available in the environment yaml file or the GET response of the corresponding environment.
After executing these commands, exit from the Docker container.

Run the following commands to restart the container:

cd /home/opc/cm_app/{CM_RESOURCE_PREFIX}/bash start_cmserver.sh <SCM_VERSION>

Confirm that the latest SCM version is up and running
```
docker ps
```