Docker S3 cleaner removes orphaned image layers from S3 backed private docker registries.
- removes orphaned images (images not part of a tagged image's ancestry)
- properly maintains repository index meta to keep the registry in a valid state
- highly configurable
- works with any s3 compatible stores
Removing images from private registries is not officially supported by Docker and a variety of things can go wrong. Use at your own risk!
docker run -it myriadmobile/docker-s3-cleaner:v1.0.1 \
-e S3_ACCESS_KEY=replace_me \
-e S3_SECRET_KEY=replace_me \
-e S3_BUCKET_NAME=my_registryS3_ACCESS_KEY- Your S3 access key.S3_SECRET_KEY- Your S3 secret key.S3_HOST- S3 compatible server host. default:s3.amazonaws.comS3_PORT- S3 compatible server port. default:443S3_IS_SECURE- Use SSL connection? default:TrueS3_BUCKET_NAME- Name of the bucket containing your registry data.DRY_RUN- WhenTrueall file operations are logged but not performed. default:False
The Docker S3 Cleaner will only remove layers that are no longer a part of a tagged hierarchy.
curl -X GET http://REGISTRY_HOST:PORT/v1/repositories/NAMESPACE/REPO/tags
curl -X DELETE http://REGISTRY_HOST:PORT/v1/repositories/NAMESPACE/REPO/tags/TAG_NAME
Note: For private repositories NAMESPACE is normally library