Ords container complains about CONN_STRING_FILE

[artm]

When attempting to run ords container in kuberntes the container complains at start up:

ERROR: CONN_STRING_FILE has not added, create a file with CONN_STRING variable and added as docker volume:
          mkdir volume ; echo 'CONN_STRING=user/password@hostname:port/service_name' > volume/conn_string.txt

This requirement isn't documented at https://container-registry.oracle.com/ords/ocr/ba/database/ords . The error message is ungrammatical. And it doesn't explain where the image expects the file (where the voulume is supposed to be mounted).

All the information in the conn string is already supplied to the container via the documented environment variables DBHOST, DBPORT, DBSERVICENAME and ORACLE_PWD. The image doesn't need the file as well. Having a dummy volume must not be a requirement for running a container.

[artm]

Workaround:

Added a small ephemeral volume (emptyDir with medium: Memory) and mounted it at /opt/oracle/variables, which is apparently the expected location. Added an init container which mounts both /etc/ords/config and /opt/oracle/variables and executes the following:

echo "CONN_STRING=$DBUSER/$ORACLE_PWD@$DBHOST:$DBPORT/$DBSERVICENAME" > /opt/oracle/variables/conn_string.txt
chown -Rv 54321 /etc/ords/config /opt/oracle/variables

/etc/ords/config is a persistent volume, but perhaps it could live on the same ephemeral volume or not be a volume all together, I'm not sure what the consequences of different scenarios would be.

DBUSER is a custom variable we added to the workload for completeness, it is only used in the above commands. The rest are as documented at https://container-registry.oracle.com/ords/ocr/ba/database/ords

[chrishoina]

@artm the ORDS team is on this. We are in the process of assuming ownership of this ORDS project, so stay tuned. Thanks!