Troubleshooting Proxy Server Settings Propagation Failure

When provisioning SCM through OCI Marketplace, the proxy server settings sometimes fail to propagate to the Docker daemon. As a result, the connection to the container registry, object store bucket, and so on fails. Because the connection with the container registry wasn't established, the SCM container doesn't start. You can confirm the issue in the /var/log/messages log file.

The following is a sample from the log file that confirms the connectivity issue with the container registry:

cloud-init: Starting cloud manager container with CM_25.1.0 tag
cloud-init: Trying to pull repository phx.ocir.io/xxxxxxxxx/cm/server ...
dockerd: time="2025-02-28T10:24:39.915338674Z" level=info msg="Attempting next endpoint for pull after error: Get 
\"https://phx.ocir.io/v2/xxxxxxxxx/cm/server/manifests/CM_25.1.0\": Get 
\"https://phx.ocir.io/20180419/docker/token?scope=repository%xxxxxxxxx%2Fcm%2Fserver%3Apull&service=phx.ocir.io\": 
net/http: request canceled while waiting for connection (Client.Timeout exceeded while awaiting headers)"
cloud-init: Get

You must manually configure the proxy settings on the VM and start the SCM container to resolve this issue, as follows:

  1. SSH into the SCM instance.
  2. Create the docker.service.d directory as follows:
    mkdir -p /etc/systemd/system/docker.service.d
  3. Create the /etc/systemd/system/docker.service.d/http-proxy.conf file with proxy configuration as follows:
    [Service]
    Environment="HTTP_PROXY=http://www-proxy-xxxx.xx.xxxxx.com:80"
    Environment="HTTPS_PROXY=http://www-proxy-xxxx.xx.xxxx.com:80"
    Environment="NO_PROXY=localhost,127.0.0.1,.internal,xxx.com,us.xxxxx.com,idc.xxxx.com,in.xxxx.com"
  4. Reload the daemon and restart the docker service as follows:
    sudo systemctl daemon-reload
    sudo systemctl restart docker
  5. Verify that the proxy configuration was successful by executing the following command:
    sudo systemctl show --property=Environment docker

    This command shows all environment variables configured for the Docker service. Search and verify that the proxy settings are correct.

  6. Start the SCM container:
    cd /home/opc/cmapp/<CM_RESOUCE_PREFIX>
    bash start_cmserver.sh <SCM version>