Why container image push to a private registry configured with docker-distribution-2.6.2-2.git48294d9.el7 and AWS S3 storage fails with an "internal server" error ?

Solution Verified - Updated -

Issue

  • Why container image push to a private registry configured with docker-distribution-2.6.2-2.git48294d9.el7 and with AWS S3 storage fails with an "internal server" error ?
[root@test certs]# podman push test.com:5000/rhel7
Getting image source signatures
Copying blob 58abc5089e71 done  
Copying blob f91d01e7b88f done  
Error: Error copying image to the remote destination: Error writing blob: Error uploading layer to https://test.com:5000/v2/rhel7/blobs/uploads/59dac86f-faf0-4fa8-ad49-e12dff16f801?_state=ylg_W6hl8y49HiJV6JCien8qAnMLLGMHwkD7ngGg1wF7Ik5hbWUiOiJyaGVsNyIsIlVVSUQiOiI1OWRhYzg2Zi1mYWYwLTRmYTgtYWQ0OS1lMTJkZmYxNmY4MDEiLCJPZmZzZXQiOjgwNDY4NTU4LCJTdGFydGVkQXQiOiIyMDIwLTEyLTI4VDA5OjMxOjA3WiJ9&digest=sha256%3Aa29d6977ff005652cc60a86c80b65321394127d99eb45b48bfe04579db7decc7: received unexpected HTTP status: 500 Internal Server Error

Environment

  • Red Hat Enterprise Linux 7
  • docker-distribution-2.6.2-2.git48294d9.el7
  • AWS S3 storage for private registry

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