# private registry Published articles for private registry. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## What Is a Container Registry and How to Use One DevFeed: [What Is a Container Registry and How to Use One]() Original publisher: [Read original article]() Author: Pramodh Kumar M Published: 2026-08-10T17:48:35Z Content type: tutorial Language: en Sources: [Kubernetes - KodeKloud Blog | DevOps, Cloud, Kubernetes, AI Tutorials & More]() Topics: [container images](), [content addressed store](), [Docker Hub](), [Dockerfile](), [supply-chain-security]() Tags: [base-images](), [cache](), [ci-cd](), [cloud](), [container-images](), [container-registry](), [containers](), [content-addressed-store](), [cryptographic](), [devops](), [docker](), [docker-hub](), [docker-login](), [docker-pull-rate-limits](), [docker-registry](), [harbor](), [image-manifest](), [image-retention-policy](), [image-scanning](), [image-tags-vs-digests](), [kubernetes](), [private-registry](), [pull-through-cache](), [reproducible-builds](), [security](), [supply-chain-security]() ### AI overview This guide explains how container registries store and distribute container images, emphasizing the distinction between mutable tags and immutable content digests. It also covers pushing, pulling, authentication, Docker Hub rate limits, caching, scanning, and retention. ### Source excerpt A tag is a bookmark somebody else can move. A digest is the image itself. Once that distinction lands, reproducible builds, supply chain security, and every it worked yesterday mystery make sense. ## Chainguard Agent Skills is now open to everyone, with a private registry to manage your internal skills DevFeed: [Chainguard Agent Skills is now open to everyone, with a private registry to manage your internal skills]() Original publisher: [Read original article]() Published: 2026-06-17T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Agent Skills](), [chainguard](), [Security](), [audit trail](), [Open Source]() Tags: [agent-skills](), [ai-agent-skills](), [audit-trail](), [chainguard](), [chainguard-agent-skills](), [chainguard-ai-agents](), [chainguard-skills](), [cursor](), [hardening](), [private-registry](), [registry](), [security]() ### AI overview Chainguard Agent Skills is now available to all users with more than 1,000 hardened community skills, a private registry for internal skills, and a closed beta for hardening first-party skills. The service is intended to help organizations securely standardize, distribute, and manage AI agent skills. ### Source excerpt Chainguard Agent Skills now offers 1,000+ hardened community skills, private registries, and beta hardening for first-party AI agent skills. ## Personal Infrastructure DevFeed: [Personal Infrastructure]() Original publisher: [Read original article]() Published: 2017-12-16T15:25:24Z Content type: article Language: en Sources: [Jessie Frazelle]() Topics: [Homelab](), [CI/CD](), [Docker](), [Jenkins](), [docker registry](), [Docker Hub](), [Dockerfile](), [GitHub](), [Bash](), [make](), [Authentication](), [Git]() Tags: [authentication](), [automation](), [bash](), [ci](), [continuous-integration](), [docker](), [docker-hub](), [docker-registry](), [dockerfiles](), [git](), [github](), [home-lab](), [infrastructure](), [jenkins](), [make](), [personal](), [private-registry]() ### AI overview A personal infrastructure overview describing self-hosted continuous integration with Jenkins, automated Jenkins DSL generation, a Postfix server, and a private Docker registry with image signing, authentication, and vulnerability scanning. ### Source excerpt This post is kind of like "part two" on my series on all the weird things I do for my personal infrastructure. If you missed "part one", you should check out Home Lab is the Dopest Lab. I run a lot of little things to make my life easier, like a CI, some bots, and a bunch of services just for the lolz. This post will go over all of those. These run scattered across my NUCs and the cloud. Let's start with the most useful. Continuous Integration I host my own continuous integration server. Yes, you guessed it... it's Jenkins. I use the Jenkins DSL plugin to keep everything in sync. You can find all my DSLs in my repo github.com/jessfraz/jenkins-dsl. This has all the configurations for views, keeps forks up to date, mirrors all my repositories to private git (more on this in git), builds all Dockerfiles to push to Docker Hub and my private registry (more on this in private docker registry) and a bunch of maintenance scripts. The Makefile in this repo calls out to bash scripts which generate new DSLs for any new GitHub repos I create. Yep I even generate the automation... There's a bunch of other fun things in there as well that you can discover by poking around yourself. I host my own postfix server alongside Jenkins. You can find the postfix docker image at r.j3ss.co/postfix or the Dockerfile. It's super minimal and less gross than literally every other postfix image in existence. You can run it with: $ docker run --restart always -d \ --name postfix \ --net container:jenkins \ -e "ROOT_ALIAS=root@blah.com" \ -e "RELAY=[smtp-relay.gmail.com]:587" \ -e "TLS=1" \ -e "MY_DESTINATION=...., localhost" \ -e "MAILNAME=blah.com" \ r.j3ss.co/postfix Private Docker Registry I host my own private docker registry with my own notary server and authentication server. Why? Well because about 4 years ago when I started using docker, Docker Hub was super slow and I came to love having my own super fast one. I still push all the images to both Docker Hub and my registry and both are signed