CRI-O does not work with HTTP_PROXY set as https:// protocol

Solution Unverified - Updated -

Issue

  • When importing images in OpenShift 3.11 using CRI-O runtime there's an error:
Error determining manifest MIME type for docker://registry.redhat.io/openshift3/ose-pod:v3.11: pinging docker registry returned: Get https://registry.redhat.io/v2/: proxyconnect tcp: net/http: TLS handshake timeout"
  • Manually pull an image using crictl fails also:
# crictl pull registry.redhat.io/openshift3/ose-node
FATA[0020] pulling image failed: rpc error: code = Unknown desc = pinging docker registry returned: Get https://registry.redhat.io/v2/: proxyconnect tcp: net/http: TLS handshake timeout

Environment

  • OpenShift Container Platform
    • 3.x
  • CRI-O runtime

Subscriber exclusive content

A Red Hat subscription provides unlimited access to our knowledgebase, tools, and much more.

Current Customers and Partners

Log in for full access

Log In

New to Red Hat?

Learn more about Red Hat subscriptions

Using a Red Hat product through a public cloud?

How to access this content