Dockerfile added

[tarampampam]

Related issue: #85

Suggested workflow for the images publishing on docker hub & GitHub containers (using GitHub actions):

name: release

on:
  release: # Docs: <https://git.io/JeBz1#release-event-release>
    types: [published]

jobs:
  docker-image:
    name: Build docker image
    runs-on: ubuntu-20.04
    steps:
      - uses: actions/checkout@v2

      - uses: gacts/github-slug@v1 # Action page: <https://github.com/gacts/github-slug>
        id: slug

      - uses: docker/setup-qemu-action@v1 # Action page: <https://github.com/docker/setup-qemu-action>

      - uses: docker/setup-buildx-action@v1 # Action page: <https://github.com/docker/setup-buildx-action>

      - uses: docker/login-action@v1 # Action page: <https://github.com/docker/login-action>
        with:
          username: aptible
          password: ${{ secrets.DOCKER_PASSWORD }}

      - uses: docker/login-action@v1 # Action page: <https://github.com/docker/login-action>
        with:
          registry: ghcr.io
          username: ${{ github.actor }}
          password: ${{ secrets.GITHUB_TOKEN }}

      - uses: docker/build-push-action@v2 # Action page: <https://github.com/docker/build-push-action>
        with:
          context: .
          file: Dockerfile
          push: true
          platforms: linux/amd64,linux/arm64,linux/arm/v6,linux/arm/v7
          tags: |
            aptible/supercronic:${{ steps.slug.outputs.version }}
            aptible/supercronic:latest
            ghcr.io/aptible/supercronic:${{ steps.slug.outputs.version }}
            ghcr.io/aptible/supercronic:latest

[tarampampam]

Friendly ping @krallin

[krallin]

While I've got push access to the repo, the release workflow is something that should probably be looked at by the Aptible folks since I don't have admin access to set up actions here.

@fancyremarker, thoughts? Note that the case for this existing is explained in #85, it's to use it as a COPY --from source (which IMO makes sense), not as a base image (which IMO does not and I think there are historical issues here explaining the reasoning)

[tarampampam]

Friendly ping @fancyremarker

[tarampampam]

Any news?

[fancyremarker]

Hi @tarampampam , sorry for the delay! To clarify, are you suggesting that the workflow in your PR message be used as .github/workflows/release.yml? I'm not clear why we'd (also) want the image.tar upload that's in tests.yml in the PR.

Assuming you're looking for us to build and host an image, we can set that up. We'd want it to be hosted on Docker Hub and Quay, our 2 registries. (We don't currently use GitHub Packages.) Our team can make that change, but first I want to make sure I'm understanding the intent here.

[tarampampam]

are you suggesting that the workflow in your PR message be used as .github/workflows/release.yml?

Yes

I'm not clear why we'd (also) want the image.tar upload that's in tests.yml in the PR

For the image testing in the next jobs, for example. Removed

[tarampampam]

Ping?