gistfile1.txt

[root@ip-10-180-34-196 new_certs]# docker version
Client:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:25:01 UTC 2015
 OS/Arch:      linux/amd64

Server:
 Version:      1.9.1
 API version:  1.21
 Go version:   go1.4.2
 Git commit:   a34a1d5
 Built:        Fri Nov 20 13:25:01 UTC 2015
 OS/Arch:      linux/amd64
[root@ip-10-180-34-196 new_certs]# docker info
Containers: 1
Images: 61
Server Version: 1.9.1
Storage Driver: devicemapper
 Pool Name: docker-202:1-17252513-pool
 Pool Blocksize: 65.54 kB
 Base Device Size: 107.4 GB
 Backing Filesystem:
 Data file: /dev/loop0
 Metadata file: /dev/loop1
 Data Space Used: 1.041 GB
 Data Space Total: 107.4 GB
 Data Space Available: 6.015 GB
 Metadata Space Used: 2.392 MB
 Metadata Space Total: 2.147 GB
 Metadata Space Available: 2.145 GB
 Udev Sync Supported: true
 Deferred Removal Enabled: false
 Deferred Deletion Enabled: false
 Deferred Deleted Device Count: 0
 Data loop file: /var/lib/docker/devicemapper/devicemapper/data
 Metadata loop file: /var/lib/docker/devicemapper/devicemapper/metadata
 Library Version: 1.02.93-RHEL7 (2015-01-28)
Execution Driver: native-0.2
Logging Driver: json-file
Kernel Version: 3.10.0-229.20.1.el7.x86_64
Operating System: CentOS Linux 7 (Core)
CPUs: 4
Total Memory: 6.897 GiB
Name: ip-10-180-34-196.staging-uswest2.ts.bmc.com
ID: EHML:DMQG:6GXY:Y3UV:4LLB:CELH:XA76:7Z3Q:ETXZ:HQLU:DXN5:SRGW
WARNING: bridge-nf-call-iptables is disabled
WARNING: bridge-nf-call-ip6tables is disabled

---


[root@ip-10-180-34-196 opt]# docker login -u <REDACTED> -p <REDACTED>-e <REDACTED> docker.ts.<REDACTED>.com:5000
WARNING: login credentials saved in /root/.docker/config.json
Login Succeeded
----

Attempt to push image to docker registry/s3

docker push docker.ts.<REDACTED>.com:5000/centos:latest
The push refers to a repository [docker.ts.<REDACTED>.com:5000/centos] (len: 1)
e9fa5d3a0d0e: Image push failed
Head https://s3-us-west-2.amazonaws.com/tsi-docker/s3/object/name/prefix/docker/registry/v2/blobs/sha256/a3/a3ed95caeb02ffe68cdd9fd84406680ae93d633cb16422d00e8a7c22955b46d4/data?X-Amz-Algorithm=AWS4-HMAC-SHA256&X-Amz-Credential=<REDACTED>%2Fus-west-2%2Fs3%2Faws4_request&X-Amz-Date=20151201T194328Z&X-Amz-Expires=1200&X-Amz-Signature=6e0bc35ead289b8a92997cbf07499247a73b2cf4d14bbc4277215ff660e09c76&X-Amz-SignedHeaders=host: x509: certificate signed by unknown authority

The solution /work around here is that the S3 certificate must be added to docker daemon registry certificates
See: distribution/distribution#426