# Oracle Management Agent Container Image
OCI Management Agent allows Oracle's Observability and Management services to be able to manage and monitor customer's resources. Complete documentation is available at [OCI Management Agent Public Documentation](https://docs.oracle.com/en-us/iaas/management-agents/index.html). OCI Management Agent container image can be deployed in a Kubernetes Cluster using helm charts using [Management Agent Helm Charts Documentation](https://github.com/oracle-quickstart/oci-management-agent/blob/main/kubernetes-monitoring/mgmtagent_helm/README.md) which will collect performance metrics from a Kubernetes cluster.
## How to use the Management Agent Container Image
1. Ensure your tenancy is configured correctly by [applying the documented prerequisites for deploying management agents](https://docs.oracle.com/en-us/iaas/management-agents/doc/perform-prerequisites-deploying-management-agents.html)
2. Create a directory on the host to store persisitent data. This directory will be bind mounted into the container at runtime.
```shell
rm -rf /oracle-management-agent
mkdir -p /oracle-management-agent
```
3. Create a local user account that will be used to run the container. This can be any user account on the host system and if the desired user already exists then this step can be skipped.
```shell
groupadd -g 9100 orclmgmtagntgrp
useradd orclmgmtagntusr -u 9200 -g 9100 -m -s /bin/bash
```
4. Follow the steps in the [Create Install Key documentation](https://docs.oracle.com/en-us/iaas/management-agents/doc/management-agents-administration-tasks.html#GUID-C841426A-2C32-4630-97B6-DF11F05D5712) to download the install key. Next, follow the steps to [Configure a Response File](https://docs.oracle.com/en-us/iaas/management-agents/doc/install-management-agent-chapter.html#GUID-5D20D4A7-616C-49EC-A994-DA383D172486) and save it locally as `input.rsp` in the current directory.
5. Copy the Install Key `input.rsp` into the directory that will be bind mounted into the container and used for persistent storage
```shell
mkdir -p /oracle-management-agent/mgmtagent_secret/
cp input.rsp /oracle-management-agent/mgmtagent_secret/
```
6. Change ownership of the directory holding persistent data to the desired user.
```shell
chown -R orclmgmtagntusr:orclmgmtagntgrp /oracle-management-agent
cp input.rsp /oracle-management-agent/mgmtagent_secret/
```
7. Start a container
```shell
export USERID=$(id -u orclmgmtagntusr)
export GROUPID=$(id -g orclmgmtagntusr)
docker run --user $USERID:$GROUPID -d --name mgmtagentcontainer1 --hostname mgmtagentcontainer1 -v /oracle-management-agent/:/opt/oracle:rw --restart unless-stopped oracle/mgmtagent-container:latest
```
## Troubleshooting
Below are some possible solutions to common issues that may occur when running the Oracle Management Agent container image
1. mkdir: cannot create directory '/opt/oracle/bootstrap': Permission denied
* Ensure the mounted bind volume exists and is accessible by the user used to run the container
* Verify the user USERID and GROUPID used match the permissions set on the mounted bind volume
* Verify the mounted bind volume exists on the host
1. Invalid argument: /opt/oracle/mgmtagent_secret/input.rsp
* Ensure the install key exists at the required location
1. Oracle Management Agent registration failures due to old state files from a prior install
* Once a Oracle Management Agent instance is deregistered that instance must be shutdown and any associated state files must be removed from the filesystem. Starting a deregistered Oracle Management Agent instance again can result in unregistered agent failures. This situation can present itself when old state files from a prior installation are present on the filesystem and made available to a new Oracle Management Agent container deployment. Run the command given below on the host filesystem to perform the necessary cleanup on the bind mount location and perform the deployment again.
```shell
rm -rf /oracle-management-agent/
```