2 KiB
Apt & Yum Repository Maintenance
A maintainer's guide to managing Docker's package repos
How to clean up old experimental debs and rpms
We release debs and rpms for experimental nightly, so these can build up. To remove old experimental debs and rpms, and ONLY keep the latest, follow the steps below.
-
Checkout docker master
-
Run clean scripts
docker build --rm --force-rm -t docker-dev:master .
docker run --rm -it --privileged \
-v /path/to/your/repos/dir:/volumes/repos \
-v $HOME/.gnupg:/root/.gnupg \
-e DOCKER_RELEASE_DIR=/volumes/repos \
docker-dev:master hack/make.sh clean-apt-repo clean-yum-repo
- Re-sign the repo with your gpg key
./hack/make/sign-repos
-
Upload the changed repos to
s3(if you host on s3) -
Purge the cache, PURGE the cache, PURGE THE CACHE!
How to get out of a sticky situation
Sh*t happens. We know. Below are steps to get out of any "hash-sum mismatch" or "gpg sig error" or the likes error that might happen to the apt repo.
NOTE: These are apt repo specific, have had no experimence with anything similar happening to the yum repo in the past so you can rest easy.
For each step listed below, move on to the next if the previous didn't work. Otherwise CELEBRATE!
-
Purge the cache.
-
Did you remember to sign the debs after releasing?
Re-sign the repo with your gpg key:
./hack/make/sign-repos
Upload the changed repo to s3 (if that is where you host)
PURGE THE CACHE.
- Run Jess' magical, save all, only in case of extreme emergencies, "you are going to have to break this glass to get it" script.
docker build --rm --force-rm -t docker-dev:master .
docker run --rm -it --privileged \
-v /path/to/your/repos/dir:/volumes/repos \
-v $HOME/.gnupg:/root/.gnupg \
-e DOCKER_RELEASE_DIR=/volumes/repos \
docker-dev:master hack/make.sh update-apt-repo
Re-sign the repo with your gpg key:
./hack/make/sign-repos
Upload the changed repo to s3 (if that is where you host)
PURGE THE CACHE.