Replies: 2 comments
-
thanks @mortag for your questions, so far harbor is an OCI registry, and we don't have any plan by now to support non-OCI compliant objects. |
Beta Was this translation helpful? Give feedback.
-
Thank you for your response regarding Harbor's support for non-OCI compliant objects. I appreciate the clarity and understand that Harbor is currently focused on OCI-compliant artifacts. However, I have a specific use case where I need to manage non-OCI packages within Harbor. Since this is not officially supported, I would like to explore the possibility of extending Harbor myself to accommodate this requirement. Could you kindly provide any hints, guidance, or suggestions on how I might approach this? For example: Are there any existing extension points or plugins in Harbor that could be leveraged for non-OCI artifacts? Would modifying the API or storage backend be the most viable approach? Are there any known community efforts or forks that have attempted something similar? Any advice or pointers you can provide would be greatly appreciated. I’m eager to contribute to the Harbor ecosystem and would be happy to share my findings or code if I succeed in implementing this functionality. Thank you again for your time and support! Best regards, |
Beta Was this translation helpful? Give feedback.
-
Harbor is an excellent OCI-compliant registry for managing container images and Helm charts. However, it lacks built-in support for popular artifact repositories such as npm, Go, and PyPI. While I’ve been using the ORAS tool to push and pull packages, I would like to use these package managers (e.g., npm) directly with Harbor.
Could you provide guidance or suggest any solutions, such as using an API gateway or other tools, to enable direct integration with npm, Go, and PyPI?
Beta Was this translation helpful? Give feedback.
All reactions