gliderlabs / gliderlabs/cmd

S3-backed image registry

Open
#48 0 comments 0 reactions 0 assignees View on GitHub
Dominant language
Go
Stars
28
Forks
4
PR merge metrics
No merged PRs in 30d

Description

* store pulled/built images here
* Not necessary until we have non-registry commands
* Costs... ECR expensive, S3 cheap
* how will it affect image pull time compared to docker hub?
* Use local registry configured with s3 backend
* Optionally local passthrough proxy registry with s3 backend
* Configure docker daemon with --registry-mirror

Contributor guide

No contributing guide indexed for this repository

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.