Huawei/dockyard

Container & Artifact Repository

Owned by Huawei

View on GitHub ↗Jump to charts ↓

Huawei/dockyard has 250+ stars and 60+ forks on GitHub, is written in Go, and was last pushed on Apr 12, 2023. Data as of . Signed-in members get hourly updates — create a free account.

Summary Information

Updated 2 hours ago
Added to GitGenius on October 10th, 2026
Created on May 11th, 2015
Open Issues & Pull Requests: 12 (+0)
GitHub issues: Enabled
Number of forks: 66
Total Stargazers: 278 (+0)
Total Subscribers: 26 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 0.3 hours
Mean response time: 15.8 hours
90th percentile: 47.0 hours
Tracked items: 3

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 7
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 3,689 days
Stale 30+ days: 7
Stale 90+ days: 0

Recent activity

Opened in 7 days: 0
Closed in 7 days: 0
Comments in 7 days: 0
Events in 7 days: 0

Top labels

No label distribution available yet.

Most active issues this week

Sign in to see which issues are moving.
Sign in

Detailed Description

Dockyard is a container and artifact repository that stores and distributes container images, software artifacts, and virtual machine images for KVM, XEN, and VirtualBox.

The tool addresses the need for organizations to manage container images and artifacts without relying on external registries. It supports multiple distribution protocols including Docker Registry V1 and V2, as well as App Container Image Discovery. Beyond containers, it handles software artifacts in formats like JAR and WAR files, and virtual machine images across different hypervisors. The system provides encryption, verification, and vulnerability analysis capabilities for stored content, with authentication and authorization controls to manage public and private repositories. It can integrate with mainstream object storage services such as Amazon S3 and Google Cloud Storage, or use its built-in object storage for simpler deployments. A web UI provides access to all functions.

Organizations should consider Dockyard if they want to operate their own container image hub rather than depend on external services, or if they need to manage container images alongside other software artifacts and virtual machine images in a unified system. The tool suits teams seeking to reduce the operational burden of managing multiple artifact types across different storage backends. The README targets users who want alternatives to Docker Hub and those looking to centralize artifact management.

The project accepts contributions through pull requests directed to the develop branch and uses Travis CI for automated testing. The maintainers require contributors to sign commits with the Developer Certificate of Origin and use their real names in commit messages. Support is available through an issue tracker and a Google Groups mailing list for the project community.