https://github.com/lightsofapollo/docker-registry-caching
Prototype for docker registry / caching for test infrastructure.
https://github.com/lightsofapollo/docker-registry-caching
Last synced: 8 months ago
JSON representation
Prototype for docker registry / caching for test infrastructure.
- Host: GitHub
- URL: https://github.com/lightsofapollo/docker-registry-caching
- Owner: lightsofapollo
- Created: 2014-03-11T04:00:39.000Z (over 12 years ago)
- Default Branch: master
- Last Pushed: 2014-03-11T23:19:04.000Z (over 12 years ago)
- Last Synced: 2024-12-27T15:12:51.111Z (over 1 year ago)
- Language: JavaScript
- Size: 6.39 MB
- Stars: 3
- Watchers: 0
- Forks: 0
- Open Issues: 0
-
Metadata Files:
- Readme: README.md
Awesome Lists containing this project
README
docker-registry-caching
=======================
Prototype for docker registry / caching for test infrastructure.
## Usage
Start it up and leave it running in your terminal:
```sh
docker run -p 8080:8080 -e AWS_ACCESS_KEY_ID=xxxx -e AWS_SECRET_ACCESS_KEY=xxx -e S3_BUCKET=s3-bucket -e 'DEBUG=*' -i -t lightsofapollo/docker-registry-node-s3
```
## Notes
This is a big hack / proof of concept I threw together late at night... my intention was to see the difference between routing the layer through an application stack (like done in the current docker registry) vs redirecting to s3 via a signed url. In my tests the download times of images was 10-30% less with this appraoch... Ideally we could use s3 directly for more operations which should be even faster.