Docker

[jhkennedy]

This sets up the mechanics for building a docker container for any PR (to ensure it builds) and and push to main or dev, and then push it to this repositories container registry. See: https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry

container images will always be tagged with the current version number, and then:

• for pushes to develop also tagged with test
• for pushes to main also tagged with latest

Note: I'm using actions I've developed and maintained here:
https://github.com/ASFHyP3/actions
Specifically:

• reusable-git-object-name.yml
• reusable-docker-ghcr.yml

The version number generated for the docker container will be the same as reported by:

git describe --dirty --tags --long --match "*[0-9]*"

which for the current state of this PR, would look like:

v0.1.0-73-g78a27fc

which breaks down to <latest-version-tag>-<commits-since-tag>-g<commit-short-hash>. This will tie any particular docker image directly to the associated commit used to build it, and the "package version" (notably, RAiDER reports a static version based on the version.txt file, which can be out of sync with the git tags; I'll tackle that in a subsequent PR).

If you're on a version tag (or the commit associated with the version tag) the version will be reported just as:

v0.1.0

as expected.

Type of change

• Bug fix (non-breaking change which fixes an issue)
• New feature (non-breaking change which adds functionality)
• Breaking change (fix or feature that would cause existing functionality to not work as expected)

Checklist:

• I have added an explanation of what your changes do and why you'd like us to include them.
• I have written new tests for your core changes, as applicable.
• I have successfully ran tests with your changes locally.
• My change requires a change to the documentation.
• I have updated the documentation accordingly.

[jhkennedy]

This right now just gives you a bash shell in the container. I suspect we'll update it to RAiDER.__main__ if/when that's available.

[jhkennedy]

Note: This action needs to be available in the default branch (dev) before it will run.

[jlmaurer]

LGTM