Monitor Container Service wizard generates script that includes localhost and cannot be used to deploy container services to nodes

Overview

As described in the Orion Platform Administrator Guide, you can use the Monitor Container Service wizard to add a container service in the Orion Web Console by:

• Connecting to the server that hosts containers,
• Generating a script for a supported container environment, such as Docker, and
• Running the script to download deployment files and deploy containers to nodes.

This article describes what to do if you log into the Orion Web Console using a LocalHost address, launch the Monitor Container Service wizard, and click Get Script, but the generated script includes an incorrect address.

Environment

• SAM 6.7 or later
• VMAN 8.03 or later

Cause

The script generated by the Monitor Container Service wizard uses the same address that was used to log into the Orion Web Console. If you logged in using localhost, that address is included in the script but cannot be executed against nodes because it is a loopback address.

Here is an example of a script generated for a Docker container service after logging into the Orion Web Console using localhost:

curl -o docker-compose.yaml http://localhost/Orion/CMAN/Services/DeploymentFile.ashx?guid=0f9420b8-8939-48e5-8134-67b1d9418c06 
sudo docker-compose up -d

Resolution

• Edit the generated script to change the localhost loopback address to the IP address of the main Orion server (for example, 192.168.0.0)
• Before adding a container service, log into the Orion Web Console using the IP address of the main Orion server instead of localhost.