Skip to main content
NetApp Knowledge Base

Harbor fails to store data on Ontap S3 when default port is specified in config

  1. Last updated
  2. Save as PDF
Views:
62
Visibility:
Public
Votes:
0
Category:
ontap-9
Specialty:
nas
Last Updated:

Applies to

  • Onatp S3
  • Harbor (docker registry)

Issue

Using ontap S3 as a backend for harbor registry fails when the harbor configuration contains a default port for the Endpoint in the harbor.yml configuration file.
 
For example:
storage_service:
s3:
  accesskey: XXXXXXXXXXXXXXX
  secretkey: YYYYYYYYYYYYYYYYYYYYYYYYYYYYYYY
  bucket: mybucket1
  regionendpoint: http://192.168.0.132:80 <--

 

 

Sign in to view the entire content of this KB article.

New to NetApp?

Learn more about our award-winning Support

NetApp provides no representations or warranties regarding the accuracy or reliability or serviceability of any information or recommendations provided in this publication or with respect to any results that may be obtained by the use of the information or observance of any recommendations provided herein. The information in this document is distributed AS IS and the use of this information or the implementation of any recommendations or techniques herein is a customer's responsibility and depends on the customer's ability to evaluate and integrate them into the customer's operational environment. This document and the information contained herein may be used solely in connection with the NetApp products discussed in this document.