container-tagbot 3.1.0

Retags a Container in a Container Registry without the need for Docker

Tagbot

Tagbot retags OCI Container Images without needing a full Docker Pull / Docker Push workflow by working directly with the registry API.

Usage

Local Usage

tagbot \
    --username example \
    --password password \
    --source example.azurecr.io/debian:latest \
    --tags v1.0.0,1.0.0

This would add an additional tag of v1.0.0 to example.azurecr.io/debian:latest. The container image can then be pulled with either example.azurecr.io/debian:latest, example.azurecr.io/debian:v1.0.0, or example.azurecr.io/debian:1.0.0

GitHub Actions Usage

name: release

on:
  push:
    tags: ["v[0-9]+.[0-9]+.[0-9]+"]

jobs:
  release:
    uses: binkhq/tagbot/.github/workflows/retag.yaml@master
    with:
      username: example
      source: example.azurecr.io/${{ github.event.repository.name }}:${{ github.ref_name }}
      tags: ${{ matrix.environment }}-v1.0.0,${{ matrix.environment }}
      envirnment:  ${{ matrix.environment }}
    secrets:
      password: ${{ secrets.ACR_BINKCORE_PASSWORD }}
    strategy:
      matrix:
        environment: [staging, production]

FAQ

• Whats going on with ghcr.io/binkhq/tagbot?
  • This still exists, but is formally deprecated and will no longer recieve updates or support
• Are Registries other than Azure Container Registry supported?
  • Azure Container Registry is the only officially supported Registry, but other simple registries like Docker Hub are expected to work just fine.