Alex,

When I replicate and debug your signing action, it appears like the image in question is protected with authentication.  Is that correct?

or perhaps is kept under a v1 schema?

check_v1_registry → requests.get(v1_url); what is the v1_url here?

Wild guess would be that this is an attempt to connect to a HTTP (non-TLS) server using HTTPS.

(And I can’t see any connection to skopeo.)

(In reply to Miloslav Trmač from comment #7)
> check_v1_registry → requests.get(v1_url); what is the v1_url here?
> 
> Wild guess would be that this is an attempt to connect to a HTTP (non-TLS)
> server using HTTPS.
> 
> (And I can’t see any connection to skopeo.)

discussing about this with Brent, adding "--tls-verify=false" in skopeo solves this error.

Still discussing with Brent on the best approach to silence/prompt this error in the atomic CLI

> adding "--tls-verify=false" in skopeo solves this error.

Fascinating. But this is till a Python traceback.

Based on feedback and discussions, this has a proposed fix ->https://github.com/projectatomic/atomic/pull/621.

In short, agreement with Miloslav and Antonio to use --tls-verify=false until we can accurately get the list of insecure registries from the docker configuration (including dealing with CIDR notation).

Since the problem described in this bug report should be
resolved in a recent advisory, it has been closed with a
resolution of ERRATA.

For information on the advisory, and where to find the updated
files, follow the link below.

If the solution does not work for you, open a new bug report.

https://rhn.redhat.com/errata/RHBA-2016-2628.html