OPMS v10.4.0.2 - selenoid -docker - status failed

book

Article ID: 197275

calendar_today

Updated On:

Products

CA App Synthetic Monitor NIMSOFT CLOUD USER EXPERIENCE MONITOR DX Application Performance Management

Issue/Introduction

We're seeing the following docker error:

systemctl status docker.service -l
● docker.service - Docker Application Container Engine
   Loaded: loaded (/usr/lib/systemd/system/docker.service; enabled; vendor preset: disabled)
  Drop-In: /usr/lib/systemd/system/docker.service.d
           └─docker-defaults.conf
        /etc/systemd/system/docker.service.d
           └─http-proxy.conf
   Active: active (running) since Fri 2020-07-31 09:45:21 EDT; 8min ago
     Docs: https://docs.docker.com
 Main PID: 54593 (dockerd)
    Tasks: 18
   Memory: 52.9M
   CGroup: /system.slice/docker.service
           └─54593 /usr/bin/dockerd -H fd:// --containerd=/run/containerd/containerd.sock --bip x.x.x.x/16

dockerd[54593]: time="2020-07-31T09:52:48.221859442-04:00" level=error msg="Handler for POST /v1.24/images/create returned error: Get https://registry-1.docker.io/v2/: Proxy Authentication Required"



Our OPMS  connects via corporate proxy and we're able to successfully test connectivity out to the internet.

curl -v -x http://x.x.x.x:8080 https://registry-1.docker.io/v2/
* About to connect() to proxy x.x.x.x port 8080 (#0)
*   Trying x.x.x.x...
* Connected to x.x.x.x (x.x.x.x) port 8080 (#0)
* Establish HTTP proxy tunnel to registry-1.docker.io:443
> CONNECT registry-1.docker.io:443 HTTP/1.1
> Host: registry-1.docker.io:443
> User-Agent: curl/7.29.0
> Proxy-Connection: Keep-Alive
>
< HTTP/1.1 200 Connection established
<
* Proxy replied OK to CONNECT request
* Initializing NSS with certpath: sql:/etc/pki/nssdb
*   CAfile: /etc/pki/tls/certs/ca-bundle.crt
  CApath: none
* SSL connection using TLS_ECDHE_RSA_WITH_AES_128_GCM_SHA256
* Server certificate:
*       subject: CN=*.docker.io
*       start date: May 23 00:00:00 2020 GMT
*       expire date: Jun 23 12:00:00 2021 GMT
*       common name: *.docker.io
*       issuer: CN=Amazon,OU=Server CA 1B,O=Amazon,C=US
> GET /v2/ HTTP/1.1
> User-Agent: curl/7.29.0
> Host: registry-1.docker.io
> Accept: */*
>
< HTTP/1.1 401 Unauthorized
< Content-Type: application/json
< Docker-Distribution-Api-Version: registry/2.0
< Www-Authenticate: Bearer realm="https://auth.docker.io/token",service="registry.docker.io"
< Date: Fri, 31 Jul 2020 13:57:43 GMT
< Content-Length: 87
< Strict-Transport-Security: max-age=31536000
<
{"errors":[{"code":"UNAUTHORIZED","message":"authentication required","detail":null}]}
* Connection #0 to host x.x.x.x left intact

We're able to reach the page, but appears that the OPMS is unable to authenticate to this page in order to download its dependencies. 





Cause

The selenoid-docker was in failed state due to proxy authenication required error as per the /var/log/messages file.

Environment

Release :10.4.0.2

Component : WMAPP : CA APP SYNTHETIC MONITOR (WATCHMOUSE)

Resolution

The selenoid-docker was in failed state due to proxy authenication required error as per the /var/log/messages file.




We review etc/systemd/system/docker.service.d/http-proxy.conf and it contain 

[Service]
Environment="HTTP_PROXY=http://proxy.example.com:80"


The above entries didn't work but I review the link http://docs.docker.oeynet.com/engine/admin/systemd/#httphttps-proxy


This doc show a "/" after the port

[Service]
Environment="HTTP_PROXY=http://proxy.example.com:80/"

 
Once this changed was made and docker restarted, all containers are now up and running.