How to regularly clean up docker private server images

Using CI to build docker images for release has greatly improved everyone's version release efficiency, so the image repository has expanded rapidly. In order to relieve disk pressure, we need to set some cleanup strategies.

The cleanup strategies for different Docker images should be different. For example, the latest five versions of images are retained by default, all tool images are retained, and business images are retained for one month.

The simple way to keep 5 images is as follows:

Download https://github.com/mlabouardy/nexus-cli and use the cli to perform the removal.

download

wget https://s3.eu-west-2.amazonaws.com/nexus-cli/1.0.0-beta/linux/nexus-cli
chmod +x nexus-cli

Configuration

./nexus-cli configure 

Finally, the .credentials file will be created in this directory

# Nexus Credentials
nexus_host = "http://nexus.demo.com"
nexus_username = "admin"
nexus_password = "adminpass"
nexus_repository = "your-docker-private-repo"

Note that the host and port of nexus filled in the host are not the port of the repo corresponding to docker.

nexus_repository is the repo corresponding to docker.

View Mirror

./nexus-cli image ls

Keep the last 5

./nexus-cli image delete -name mlabouardy/nginx -keep 5

Comprehensive script

clean.sh

image_file=image.txt
CLI_HOME=/data/nexus3
KEEP_VERSION_NUM=5

$CLI_HOME/nexus-cli image ls > $image_file
sed -i '$d' $image_file


cat $image_file | while read line
do
 echo "Clean up $line"
 $CLI_HOME/nexus-cli image delete -name $line -keep $KEEP_VERSION_NUM
done

Scheduled tasks

crontab -e

0 2 * * * sh /data/nexus3/clean.sh

Create a nexus task

think

As mentioned earlier, different retention strategies should be selected for different images. Of course you can't just keep 5. For example, a tool image may be developed very diligently, but the application may still be an old version. For business images, n releases were made in one day, and n images were added. How to maintain these versions?

A rough idea is to standardize the image name, such as adding prefixes such as tools-, biz-, etc.

Divided into different repos. For tools, use a separate repo, and for each business, use its own repo. Different retention policies are applied to different repos.

Summarize

The above is the method of regularly cleaning up docker private server images introduced by the editor. I hope it will be helpful to everyone. If you have any questions, please leave me a message and the editor will reply to you in time. I would also like to thank everyone for their support of the 123WORDPRESS.COM website!
If you find this article helpful, please feel free to reprint it and please indicate the source. Thank you!