Images left from tagging

[floriancircly]

Hi all.

After running the tagging job with anothrNick/github-tag-action I see a built docker image which seems a bit off because it always has the same container id and there is no obvious use for the image (after digging in the docker history I found out that the container originated from github-tag-action). Is the image necessary to create the tags and should I do the clean up manually?

jobs:
  Create_Tag:
    runs-on: [...]
    steps:
      - uses: actions/checkout@v3
        with:
          fetch-depth: "0"
      - name: Bump version and push tag
        uses: anothrNick/github-tag-action@1.67.0
        env:
          GITHUB_TOKEN: ${{ secrets.GITHUB_TOKEN }}
          WITH_V: true
          DEFAULT_BUMP: patch
          RELEASE_BRANCHES: main
          PRERELEASE_SUFFIX: dev
          PRERELEASE: true
          INITIAL_VERSION: 1.0.0

Thank you so much for your support!

[sbe-arg]

We never created images. We docker run from dockerfile.

[sbe-arg]

@sammcj had a go #225 in that pr but we didn't go can't remember context

[floriancircly]

Maybe this helps?

I get this image each time i trigger the workflow. The "LABEL maintainer=Nick Sjostrom" line made me realize the images originate from this package.

[sbe-arg]

We could build images to save a few seconds of runners but the runners are billed per minute it does not really save any money and we have to continuously update the images and retrofit image builds historically to make sure they don't run with vulnerabilities from the compliance point of view. Unsure if this is the way to go.

[sbe-arg]

If you are running self hosted you could run docker prune post this action if the docker host storage is creating headaches.