# Docker Hub Docker Hub is a container registry for storing, managing, and sharing Docker images. This is one page of public article previews, not the complete archive. Follow Next page to continue. Summaries are not the original full articles. ## Moving from Minimus to Docker Hardened Images DevFeed: [Moving from Minimus to Docker Hardened Images]() Original publisher: [Read original article]() Author: Vishrut Iyengar Published: 2026-08-25T22:27:06Z Content type: article Language: en Sources: [Docker]() Topics: [Docker Hardened Images](), [migration](), [Docker](), [supply-chain-security](), [Docker Hub](), [Open Source](), [Debian](), [Artificial Intelligence]() Tags: [apache](), [ci](), [community](), [debian](), [docker](), [docker-hardened-images](), [docker-hub](), [enterprise](), [guide](), [migration](), [open-source](), [products](), [security](), [solutions](), [supply-chain](), [vulnerabilities]() ### AI overview Docker explains how Minimus customers can migrate to Docker Hardened Images before the Minimus registry goes offline on October 22, 2026. The article highlights the 60-day maintenance window, free migration assistance, DHI's open-source Apache 2.0 catalog, and a drop-in migration process centered on updating Dockerfile FROM lines. ### Source excerpt The Minimus registry goes offline on October 22. Here is the migration path, the free help Docker is offering, and where to start. ## Docker Verified Publisher Applications Are Now Self-Serve DevFeed: [Docker Verified Publisher Applications Are Now Self-Serve]() Original publisher: [Read original article]() Author: Dan Berezin Stelzer Published: 2026-08-20T17:00:00Z Content type: article Language: en Sources: [Docker]() Topics: [Docker Hub]() Tags: [analytics](), [applications](), [developers](), [docker](), [docker-hub](), [docker-verified-publisher](), [docker-verified-publisher-program](), [open-source](), [products]() ### AI overview Docker Hub now offers a self-service application process for Docker Verified Publisher status. Approved publishers receive verified status, prioritized ranking, and analytics reporting. ### Source excerpt Apply to become a Docker Verified Publisher (DVP) now directly through Docker Hub. Get your verified content seen first by devs looking for trusted options. ## 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. ## Why Trusted Software Supply Chains Matter More Than Zero-CVE Container Claims DevFeed: [Why Trusted Software Supply Chains Matter More Than Zero-CVE Container Claims]() Original publisher: [Read original article]() Published: 2026-01-15T00:00:00Z Content type: opinion Language: en Sources: [Chainguard: Unchained]() Topics: [Security](), [container-security](), [container images](), [Docker Hub](), [Containers](), [Docker](), [Software]() Tags: [ceo](), [chainguard](), [chainguard-containers](), [chainguard-images](), [chainguard-libraries](), [container-images](), [docker](), [docker-hub](), [docker-images](), [echo-security](), [hardened-images](), [hardening](), [minimus](), [rapidfort](), [secure-by-default](), [security](), [software-supply-chain-security](), [wiz-images](), [zero-cves]() ### AI overview Chainguard CEO Dan Lorenc argues that container security depends on trusting the origins and build processes of software, rather than relying primarily on post-hoc image hardening or zero-CVE claims. ### Source excerpt Chainguard CEO Dan Lorenc explains why real security comes from trusted, from-source software supply chains, not post-hoc hardening or zero-CVE promises. ## Gradle Now Maintains the Official Docker Image DevFeed: [Gradle Now Maintains the Official Docker Image]() Original publisher: [Read original article]() Author: Laura Kassovic Published: 2025-09-15T04:00:00Z Content type: release Language: en Sources: [The Gradle Blog]() Topics: [Gradle](), [Docker Image](), [Docker](), [Docker Hub](), [CI/CD](), [GitHub Actions](), [GitLab](), [Jenkins]() Tags: [ci-cd](), [docker](), [docker-hub](), [docker-image](), [github](), [github-actions](), [gitlab](), [gradle](), [jenkins](), [open-source](), [releases](), [support]() ### AI overview Gradle is now the official maintainer of the Gradle Docker image on Docker Hub. The article explains that the image will be kept current with Gradle releases, including security updates, while its usage, CI workflows, and community support continue to evolve. ### Source excerpt We're excited to announce we're now the official maintainer of the Gradle image on Docker Hub. For years, developers have relied on the Gradle Docker image to run builds in containers and CI/CD pipelines. Originally created and maintained by community contributor Keegan Witt, this image became a trusted resource for thousands of teams. Today, we're bringing it under the Gradle organization to ensure it remains reliable, up to date, and aligned with Gradle's release cadence. Why this Matters Docker is a critical part of modern software delivery. Many teams build and test their projects in containerized environments, and CI/CD platforms like GitHub Actions, GitLab CI, and Jenkins depend on official images to provide consistency and trust. By becoming the official maintainer of the Gradle Docker image, we can: Provide timely updates for each Gradle release, including security fixes Ensure alignment with the official Gradle -bin distributions Collaborate with the community to evolve the image for new use cases Provide support through the standard support channels (Slack and Community Forum) This also reduces the burden on individual contributors who've generously kept the image running until now. A big Thank You We want to recognize Keegan Witt, who has maintained the Gradle Docker image for years. His diligent work ensured developers could trust the image long before it became officially supported. We're grateful for his contributions and stewardship! What to Expect Going Forward The official Gradle Docker image will continue to be published under hub.docker.com/_/gradle. Images will be kept aligned with Gradle releases to the greatest extent possible. We'll review and evolve best practices for image usage, including improvements for CI workflows and ephemeral build environments. Using the Image Try the latest official image today: docker pull gradle:latest Or specify a versioned tag: docker pull gradle:9.0.0-jdk17 Get Involved The Gradle Docker image remains open sour ## Guardcraft: A Minecraft Java Server with Zero CVEs DevFeed: [Guardcraft: A Minecraft Java Server with Zero CVEs]() Original publisher: [Read original article]() Published: 2025-02-28T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard](), [Docker](), [Containers](), [Vulnerabilities](), [grype](), [Docker Hub](), [Security](), [Ubuntu](), [Linux](), [Steam Deck]() Tags: [bedrock](), [chainguard](), [chainguard-containers](), [chainguard-images](), [container](), [container-image](), [containers](), [docker](), [docker-hub](), [grype](), [guardcraft](), [linux](), [security](), [steam-deck](), [vulnerabilities](), [zero-cves]() ### AI overview The article describes building a Minecraft Java server with a Chainguard Image. It compares a popular Ubuntu-based Docker Hub image with the Chainguard approach, highlighting the former's 165 unresolved CVEs and the latter's stated result of zero CVEs. ### Source excerpt We built a Minecraft Java server using a Chainguard Image, resulting in zero CVEs and a whole lot of fun! ## Subtraction by addition: Leaner images, safer code DevFeed: [Subtraction by addition: Leaner images, safer code]() Original publisher: [Read original article]() Published: 2024-03-29T00:00:00Z Content type: comparison Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [Docker Hub](), [Security]() Tags: [chainguard-images](), [comparison](), [container-image](), [cves](), [docker-hub](), [image-cve](), [secure-minimal-image]() ### AI overview The article compares Chainguard Images with commonly used container images for Python, kubectl, openjdk, and golang. It reports substantially smaller image sizes and zero listed CVEs in the examples, while explaining that reducing vulnerability noise can help security teams identify meaningful risks. ### Source excerpt Learn how adding a few characters to your image names with Chainguard Images can slash image sizes by 93% and drop CVEs to zero. ## How old are Official Docker images? 2024 Edition DevFeed: [How old are Official Docker images? 2024 Edition]() Original publisher: [Read original article]() Author: Tom Published: 2024-03-24T00:00:00Z Content type: article Language: en Sources: [Tomasz Gągor]() Topics: [Docker](), [docker images](), [Docker Hub](), [centos](), [Debian](), [Ubuntu](), [openjdk](), [Bash](), [Script](), [deprecated]() Tags: [bash](), [centos](), [centos-docker-image](), [debian](), [debian-docker-image](), [deprecated](), [docker](), [docker-hub](), [docker-image-age](), [docker-image-updates](), [docker-images](), [dockerfiles](), [eclipse](), [end-of-life](), [images](), [official-docker-images](), [openjdk](), [script](), [ubuntu](), [ubuntu-docker-image]() ### AI overview An analysis of the age and update status of official Docker images in 2024. It reports that modern OS images are generally reasonably current, while CentOS and OpenJDK images have reached important lifecycle or maintenance milestones. ### Source excerpt Discover the current age and update status of various official Docker images, including CentOS, Ubuntu, and Debian, in the 2024 edition of this analysis. ## Chainguard Images now available on Docker Hub DevFeed: [Chainguard Images now available on Docker Hub]() Original publisher: [Read original article]() Published: 2024-03-14T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [Docker Hub](), [Docker Verified Publisher](), [container images](), [Security](), [supply-chain-security](), [Open Source]() Tags: [chainguard](), [chainguard-images](), [container-images](), [developer](), [docker](), [docker-hub](), [docker-hub-verified-publisher](), [docker-verified-publisher](), [dockerhub](), [hardened-images](), [open-source](), [security](), [software-supply-chain](), [verified-publisher]() ### AI overview Chainguard Images are now available on Docker Hub after Chainguard joined the Docker Verified Publisher program. The partnership gives developers access to minimal, secure, hardened images for open source and cloud-native projects, with guidance for finding and pulling verified images. ### Source excerpt Chainguard Images joins Docker Hub as a Verified Publisher, offering developers secure, hardened images for open source projects. ## Building minimal and low CVE images for compiled languages DevFeed: [Building minimal and low CVE images for compiled languages]() Original publisher: [Read original article]() Published: 2024-02-27T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [chainguard images](), [Containers](), [Docker](), [Dockerfile](), [Go Language](), [Vulnerabilities](), [Docker Hub](), [Debian](), [Ubuntu]() Tags: [chainguard](), [chainguard-images](), [compiled-language](), [containers](), [deployment](), [distroless](), [docker](), [docker-hub](), [dockerfiles](), [dockerhub](), [go](), [vulnerabilities]() ### AI overview This article demonstrates how to build smaller, lower-CVE container images for compiled languages by separating build and runtime concerns and replacing full Debian or Ubuntu bases with Chainguard Images. A Go web server example reduces the image from 892 MB to 775 MB and eliminates the reported CVEs after a one-line base-image change. ### Source excerpt Leverage Chainguard's insights to forge low-CVE, compact images for compiled languages, boosting your security posture. ## New year, new image: Introducing the Chainguard Images Directory DevFeed: [New year, new image: Introducing the Chainguard Images Directory]() Original publisher: [Read original article]() Published: 2023-12-13T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [Docker Hardened Images](), [Docker Hub](), [vulnerability](), [Security]() Tags: [chainguard](), [chainguard-images](), [chainguard-images-directory](), [common-vulnerabilities-and-exposures](), [container-image-registry](), [container-images](), [digestabot](), [security](), [vulnerability]() ### AI overview Chainguard introduces an updated Images Directory for discovering and using its minimal, hardened container images. The release also adds Security Advisories with information about CVE mitigation and introduces digestabot, a free GitHub Action for keeping Developer Images current. ### Source excerpt Discover how the updated Chainguard Images Directory simplifies finding container images and critical vulnerability advisories. ## Chainguard Academy adds image vulnerability comparison pages DevFeed: [Chainguard Academy adds image vulnerability comparison pages]() Original publisher: [Read original article]() Published: 2023-08-23T00:00:00Z Content type: release Language: en Sources: [Chainguard: Unchained]() Topics: [Vulnerabilities](), [container images](), [chainguard images](), [vulnerability management](), [Docker Hub](), [Security]() Tags: [chainguard-academy](), [chainguard-images](), [container](), [container-images](), [cves](), [docker-hub](), [security](), [vulnerabilities](), [vulnerability]() ### AI overview Chainguard Academy has added image vulnerability comparison pages that show 30 days of vulnerability scan data for external images and Chainguard Images. The article explains that routine package updates reduce only a small share of vulnerabilities in popular images and presents the comparisons as a reference for evaluating image security. ### Source excerpt Dive into Chainguard Academy's new image vulnerability comparisons, shedding light on 306 CVEs for a safer container ecosystem. ## The zero CVE challenge: Can official Docker Hub images pass the test? DevFeed: [The zero CVE challenge: Can official Docker Hub images pass the test?]() Original publisher: [Read original article]() Published: 2023-08-03T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Docker](), [Docker Hub](), [container-security](), [Vulnerabilities](), [Debian](), [Containers](), [grype]() Tags: [container-security](), [cve](), [cves](), [debian](), [docker](), [docker-hub](), [docker-hub-image](), [docker-images](), [grype](), [image-cves](), [security](), [software](), [vulnerabilities]() ### AI overview An analysis of ten widely used official Docker Hub images found that updating all operating-system packages reduced vulnerability counts by less than 6% on average. Approximately 98% of the vulnerabilities were associated with Debian-based packages, and the average image still had 225 vulnerabilities after updates. ### Source excerpt Uncover the findings of the Zero CVE Challenge on Official Docker Hub Images, a step towards secure containerization. ## Enforce against vulnerability sprawl with up-to-date images DevFeed: [Enforce against vulnerability sprawl with up-to-date images]() Original publisher: [Read original article]() Published: 2023-05-03T00:00:00Z Content type: article Language: en Sources: [Chainguard: Unchained]() Topics: [Vulnerabilities](), [chainguard images](), [Docker Hub](), [container images](), [Containers](), [open-source-security](), [Security](), [Open Source]() Tags: [chainguard-images](), [container-images](), [containers](), [development](), [docker-hub](), [hardened-images](), [image-scanning](), [security](), [vulnerability]() ### AI overview This article reports on a 60-day Chainguard analysis comparing vulnerability accumulation in six popular Docker Hub images with six equivalent Chainguard Images. It recommends frequent image rebuilds and minimal, hardened containers to reduce vulnerability sprawl, security risk, and triage effort. ### Source excerpt 60-day study by Chainguard reveals vulnerability differences in Docker Hub vs. Chainguard Images. ## Docker Hub policy changes create risks for community image publishers DevFeed: [Docker Hub policy changes create risks for community image publishers]() Original publisher: [Read original article]() Author: HTTP Toolkit; Tim Perry Published: 2023-03-17T11:00:00Z Content type: article Language: en Sources: [HTTP Toolkit]() Topics: [Docker Hub](), [Docker](), [Self-hosted](), [hosting](), [Monitoring]() Tags: [docker](), [docker-registry](), [monitoring](), [registry](), [self-hosting]() ### AI overview This commentary examines Docker Hub policy changes affecting community-run image publishers. It explains the impact on publishing control and considers self-hosting or migrating to another hosted Docker registry. ### Source excerpt As you may have seen, Docker Hub made a dramatic shift in policy this week, and effectively gave a 30 day eviction notice to almost all community-run images. They've now made an apology to 'clarify' a few details, and helpfully take some of the hard edges off, but this still highlights a big problem. Fortunately, there are solutions. As initially described, this would've been catastrophic: Docker Hub has been used as the default host in tooling, tutorials, demos, blog posts, scripts, deployment definitions, CI builds and more for many years, and all those references were going to break - a self-inflicted left-pad for the Docker ecosystem. In their updated policy, it appears they now won't remove any existing images, but projects who don't pay up will not be able to publish any new images, so they've effectively lost control of the namespace they used to deploy to their communities unless they purchase a full team subscription. Many will not do so. This is an interesting challenge. Even if the existing images aren't removed, the direction of travel for Docker Hub is now clear: they don't want to host the core of the Docker community any more, no more freebies, pay up or go elsewhere (not unreasonable, but something of a rugpull after a full decade of the opposite). As a small/open-source/community/hobbyist image publisher, or if you depend on Docker Hub for free image publishing in any capacity, you now have a problem. They don't want you there. You're explicitly not their audience, and the rules will likely tighten further. This isn't unreasonable - it's their service and hosting isn't free - but it's worth considering explicitly and reacting accordingly. If you're not a paying Docker Hub customer, it's time to leave Docker Hub. The hard part is what to do instead. Self-hosting a registry is not free, and it's more work than it sounds: it's a proper piece of infrastructure, and comes with all the obligations that implies, from monitoring to promptly applying securit ## Docker requires some organisation accounts to upgrade to a paid plan or lose their images DevFeed: [Docker requires some organisation accounts to upgrade to a paid plan or lose their images]() Original publisher: [Read original article]() Author: Alex Ellis Published: 2023-03-15T10:56:54Z Content type: opinion Language: en Sources: [Alex Ellis' Blog]() Topics: [Docker Hub](), [Open Source](), [Maintainers](), [Docker]() Tags: [community](), [cost](), [docker](), [docker-hub](), [github](), [maintainers](), [open-source](), [opinion]() ### AI overview The article discusses Docker's notice that some Docker Hub organisation accounts must upgrade to a paid team plan or risk deletion of the account and its images. It says the change affects organisation accounts used by open-source communities, while personal accounts were unchanged, and criticizes Docker's communication and cost. ### Source excerpt This controversial decision coupled with poor messaging has created anxiety the Open Source community. Learn what's happening and how we can move forward. ## Running a Quarkus Native Application on Render DevFeed: [Running a Quarkus Native Application on Render]() Original publisher: [Read original article]() Published: 2022-11-28T10:45:00Z Content type: tutorial Language: en Sources: [Gunnar Morling]() Topics: [Quarkus](), [Cloud](), [Docker](), [Docker Hub](), [GitHub Actions]() Tags: [cloud](), [docker](), [docker-hub](), [github](), [github-actions](), [native](), [quarkus]() ### AI overview This tutorial explains how to deploy a Quarkus application compiled with GraalVM as a native application on Render. It uses Docker for deployment and discusses Render's free-tier constraints, Docker Hub access, and a GitHub Actions-based workflow. ### Source excerpt Table of Contents Java Applications on Render Configuration Details Docker Hub Access Token GitHub Actions This is a quick run down of the steps required for running JVM applications, built using Quarkus and GraalVM, on Render. Render is a cloud platform for running websites and applications. Like most other comparable services such as fly.io, it offers a decent free tier, which lets you try out the service without any financial commitment. Unlike most other services, with Render, you don't need to provide a credit card in order to use the free tier. Which means there's no risk of surprise bills, as often is the case with pay-per-use models, where a malicious actor could DDOS your service and drive up cost for consumed CPU resources or egress bandwidth indefinitely. ## Using Docker Containers to Run Development Tools Without Local Installation DevFeed: [Using Docker Containers to Run Development Tools Without Local Installation]() Original publisher: [Read original article]() Author: andrew@nystudio107.com (Andrew Welch) Published: 2021-11-02T15:42:00Z Content type: tutorial Language: en Sources: [nystudio107 | Articles on modern web development.]() Topics: [Docker](), [Containers](), [Docker Image](), [Docker Hub](), [Command-line interface](), [Shell]() Tags: [command-line](), [computer](), [containerization](), [devops](), [docker](), [docker-hub](), [embracing](), [flexible](), [gives](), [messy](), [robust](), [setup](), [things](), [tools](), [transportable]() ### AI overview This tutorial explains how to use Docker containers to run development tools without installing them directly on a computer. It describes the benefits of disposable, version-specific, self-contained images and introduces Docker Hub and shell aliases. ### Source excerpt Embracing Docker for All The Things gives you a more flexible, robust, and transportable way to use tools on your computer without messy setup ## Multi-platform Docker images with GoReleaser, Podman and GitHub Actions DevFeed: [Multi-platform Docker images with GoReleaser, Podman and GitHub Actions]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2021-08-01T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Docker](), [podman](), [GitHub Actions](), [Docker Hub](), [GitHub Container Registry](), [personal access token]() Tags: [distribution](), [docker](), [docker-images](), [github-actions](), [github-container-registry](), [manifest](), [personal-access-token](), [podman]() ### AI overview A tutorial showing how to build and publish multi-platform container images with GoReleaser, Podman, and GitHub Actions. It explains rootless, daemonless Podman usage, multi-platform builds and manifests, GitHub Container Registry authentication with a personal access token, and release automation. ### Source excerpt A few months ago, I published a post on Multi-platform Docker images with GoReleaser and GitHub Actions. Today's post has the same idea, but using Podman instead of Docker. ## Docker Hub pull rate limits hit Rahti DevFeed: [Docker Hub pull rate limits hit Rahti]() Original publisher: [Read original article]() Author: Unknown (noreply@blogger.com) Published: 2021-03-04T08:59:00Z Content type: article Language: en Sources: [CSC - IT Center For Science - Cloud Team]() Topics: [Docker Hub](), [incident](), [Availability](), [Caching](), [Back end]() Tags: [availability](), [deployment](), [docker-container](), [docker-hub](), [incident](), [rate-limiting](), [registry]() ### AI overview This technical article describes how Docker Hub pull rate limits affected Rahti deployments and builds, and how administrators responded by recommending alternative repositories and caching or migrating images to Rahti's registry. The impact was compounded by availability problems in Rahti's own registry during a storage incident. ### Source excerpt November 2020 was an eventful month for Rahti. Our backend storage had incident that affected our production clusters image repository for many weeks. That event is well described in Allas downtime November 2020 - technical deep-dive. Just before our storage incident, 2nd of November, Docker applied "rate limiting for Docker container pulls for some users". When we tried to prepare for this in advance, it was very hard to figure out what the exact effect would be for Rahti. It took longer to resolve than we anticipated. Limits beganWe were relieved that the first day after pull rates were enforced was peaceful. Rahti was still up and running as it should. Users didn't complain about failing deployment in large amounts. Admins survived another upstream change. Eventually we received few tickets on failing builds. Our first approach was to instruct people to change their images away from Docker Hub to alternative repositories which do not have rate limiting enabled. Some users were able to migrate their images but this was not feasible solution for everyone. Still, it was a good opportunity to remind users to check what images they use. The error looks like this: Pulling image "docker.io/centos/python-38-centos7@sha256:da83741689a8d7fe1548fefe7e001c45bcc56a08bc03fd3b29a5636163ca0353" ... pulling image error : toomanyrequests: You have reached your pull rate limit. You may increase the limit by authenticating and upgrading: https://www.docker.com/increase-rate-limit Cumulative issues cause exponential griefWe gave our users instructions how to move their dependencies from public Docker Hub to Rahti image registry, How to manually cache images in Rahti's registry. This was harder in practice, as we did have issues with our own registry due to our storage incident. There were days when users suffered from both Docker Hub and Rahti internal registry availability. Those days were hard for our Rahti admins, who struggled to meet customer expectations of highly available ser ## Publish a Docker container from Bitbucket to Google Cloud Container Registry DevFeed: [Publish a Docker container from Bitbucket to Google Cloud Container Registry]() Original publisher: [Read original article]() Published: 2019-08-07T00:00:00Z Content type: tutorial Language: en Sources: [Juri Strumpflohner]() Topics: [Docker](), [bitbucket](), [Google Cloud Platform (GCP)](), [Docker Hub](), [Automation](), [Git](), [Jenkins](), [GitLab]() Tags: [automation](), [bitbucket](), [circleci](), [container-registry](), [docker](), [git](), [gitlab](), [google-cloud](), [jenkins](), [registry]() ### AI overview This tutorial explains how to configure a Bitbucket pipeline to automatically build and publish Docker container images to a private repository in Google Cloud Container Registry. It covers triggering builds from commits and Git tags, setting required environment variables, authenticating with Google Cloud, and tagging images. ### Source excerpt Lorem ipsum dolor sit amet ## 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 ## Continuous Delivery with GitHub, CircleCI, Docker and AWS Elastic Beanstalk DevFeed: [Continuous Delivery with GitHub, CircleCI, Docker and AWS Elastic Beanstalk]() Original publisher: [Read original article]() Author: Carlos Alexandro Becker Published: 2015-09-29T00:00:00Z Content type: tutorial Language: en Sources: [Carlos Becker]() Topics: [Continuous Delivery (CD)](), [CI/CD](), [Docker](), [CircleCI](), [GitHub](), [Docker Hub](), [Deployment](), [Amazon Web Services](), [Environment Variables]() Tags: [aws](), [circleci](), [continuous-delivery](), [deployment](), [docker](), [docker-hub](), [environment-variables](), [github]() ### AI overview This tutorial explains a continuous delivery setup for a Go service using GitHub, CircleCI, Docker, Docker Hub, and Amazon Elastic Beanstalk. Commits pushed to the site repository are built into Docker images, tagged with the CircleCI build number, pushed to Docker Hub, and deployed to production so deployed commits can be traced through the image and build tags. ### Source excerpt This is just a quick overview of how I did it in antibody's homepage.