Content migrated to the vRealize Orchestrator file system must follow the requirements of the new container-based appliance.

Because the vRealize Orchestrator appliance is running in a container, it has limitations regarding access to the file system. The js-io-rights.conf file still determines if a file is accessible from the vRealize Orchestrator scripting API, but you cannot use arbitrary folders in the file system. The main folder accessible to the vRealize Orchestrator service is /var/run/vco. Under the vRealize Orchestrator appliance file system, this folder is mapped under /data/vco/var/run/vco. All local files that access the vRealize Orchestrator scripting API must be moved to the specified main directory. Under the main directory, you can create subdirectories for your content.

For example, if you want to mount an external NFS volume to your vRealize Orchestrator appliance, you must mount it in /data/vco/var/run/vco/ mount_directory_path. Afterwards, the vRealize Orchestrator scripting API can access the mounted NFS volume at /var/run/vco/mount_directory_path.

Kerberos Configuration

To use a Kerberos configuration, you can only use the /data/vco/usr/lib/vco/app-server/conf/krb5.conf file. For information on Kerberos debug logging, see Enable Kerberos Debug Logging in Installing and Configuring VMware vRealize Orchestrator.