psviderski/unregistry

Push docker images directly to remote servers without an external registry

View on GitHub ↗Jump to charts ↓Open shareable report

Summary Information

Updated 1 hour ago
Added to GitGenius on September 14th, 2026
Created on June 3rd, 2025
Open Issues & Pull Requests: 21 (+0)
GitHub issues: Enabled
Number of forks: 94
Total Stargazers: 4,866 (+0)
Total Subscribers: 16 (+0)

Repository Insights (GitGenius)

Median issue/PR response: 8.2 hours
Mean response time: 3.4 days
90th percentile: 4.7 days
Tracked items: 30

Most active contributors

Sign in to see contributor activity.

Charts & Analytics

Fetching additional details & charts...

Issue Activity (beta)

Open issues: 16
New in 7 days: 0
Closed in 7 days: 0
Avg open age: 355 days
Stale 30+ days: 16
Stale 90+ days: 15

Recent activity

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

Top labels

  • bug (14)
  • documentation (1)
  • question (1)

Most active issues this week

No issue events were indexed in the last 7 days.

Detailed Description

Unregistry is a lightweight container image registry that enables pushing Docker images directly to remote servers over SSH without requiring an external registry service.

The tool solves the inefficiency of moving container images between machines. Traditional approaches force you to choose between public registries, self-hosted registry infrastructure, or inefficient full-image transfers. Unregistry works by establishing an SSH tunnel to a remote server, starting a temporary registry container there, and pushing the image through that tunnel while transferring only the layers that do not already exist on the destination. This layer-aware transfer mimics the efficiency of rsync for Docker images.

Teams managing container deployments across multiple Docker hosts should consider this tool if they want to avoid the operational burden of maintaining a dedicated registry while still achieving efficient image distribution. It suits environments where images need to move between machines under your control, particularly in private infrastructure scenarios. The tool requires Docker CLI with plugin support on the local machine and OpenSSH client connectivity to remote servers.

Development activity shows consistent engagement with the project. The maintainer actively maintains the codebase and responds to community interaction through multiple channels. The tool remains under active development with ongoing refinement of its core functionality.