Skip to content

'x509: certificate signed by unknown authority' errors when using --skip-tls option #362

@dprince

Description

@dprince

Trying to use the locally configured openshift image-registry route with 'opm registry add' commands today and the --skip-tls option doesn't seem to work.

opm registry add -b default-route-openshift-image-registry.apps.test.dprince/openstack/openstack-cluster-bundle:v0.0.5 --skip-tls --container-tool podman -d database/index.db

fails with 'x509: certificate signed by unknown authority' errors.

I am able to push and pull the same image with podman locally. So this works:

podman pull default-route-openshift-image-registry.apps.test.dprince/openstack/openstack-cluster-bundle:v0.0.5 --tls-verify=false

NOTE: as this is an openshift registry I am running login command ahead of these commands but I don't think it is related to the root cause of the error here.

Metadata

Metadata

Assignees

No one assigned

    Labels

    lifecycle/staleDenotes an issue or PR has remained open with no activity and has become stale.triage/unresolvedIndicates an issue that can not or will not be resolved.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions