Molecule test fails due to SSL error on local machine

[ibm]

Molecule test fails due to SSL error on local machine

[mew2057]

Executing a docker pull the container used by molecule yields the same result:

$ docker pull --disable-content-trust  quay.io/operator-framework/ansible-operator:v0.11.0
Error response from daemon: Get https://quay.io/v2/: x509: certificate is valid for jdunham-rh72-k8s-scale-master.com, not quay.io

[mew2057]

docker version
Client:
 Version:           18.06.3-ce
 API version:       1.38
 Go version:        go1.10.4
 Git commit:        d7080c1
 Built:             Wed Feb 20 02:24:22 2019
 OS/Arch:           linux/amd64
 Experimental:      false

Server:
 Engine:
  Version:          18.06.3-ce
  API version:      1.38 (minimum version 1.12)
  Go version:       go1.10.3
  Git commit:       d7080c1
  Built:            Wed Feb 20 02:25:33 2019
  OS/Arch:          linux/amd64
  Experimental:     false

[mew2057]

Not just quay.io:

docker pull registry.access.redhat.com/ubi8/ubi:latest
Error response from daemon: Get https://registry.access.redhat.com/v2/: x509: certificate is valid for jdunham-rh72-k8s-scale-master.com, not registry.access.redhat.com

[mew2057]

Tried cloning in my /etc/docker/certs.d and it didn't change anything.

[mew2057]

Digging deeper I think that in a cluster based kubernetes install the test-local directive might have problems.

[mew2057]

Trying to force things and it gets interesting:

export REPO="$(hostname -f):5000/"
docker pull quay.io/operator-framework/ansible-operator:v0.11.0
docker tag quay.io/operator-framework/ansible-operator:v0.11.0  ${REPO}ansible-operator:v0.11.0
docker push ${REPO}ansible-operator:v0.11.0

Then in Dockerfile:

FROM ${REPO}ansible-operator:v0.11.0

Response:

Get https://jdunham-rh72-k8s-scale-master.com:5000/v2/: x509: certificate signed by unknown authority

Smells super like a docker ssl issue.

[deeghuge]

Unit tests for new go operator is in plan which will take care of such scenarios freshly.