Automate Docker build of Feed-Discovery service with GitHub Actions

[humphd]

We're moving toward containerizing everything, and it might be time to consider using an automated container build setup with Actions so we can build and push to a registry, then automate our deployments to pull for zero-downtime updates.

GitHub has a new Docker registry, but it looks like the current Seneca-CDOT account doesn't support it? @ctyler do you know anything about CDOT's GitHub org being a "legacy" account?

I'm not sure if this is fixable or not, but it would be cool to use GitHub's storage for this. I don't think there's another registry that will let us host all these containers for free?

[birtony]

I'd be keen to look into this

[humphd]

https://docs.github.com/en/packages/working-with-a-github-packages-registry/working-with-the-container-registry

[humphd]

See #2683

[humphd]

I updated this to be about getting the feed-discovery service built and the image uploaded to the GitHub Package Registry. Once we figure this out for feed-discovery, we can move onto the others.

[humphd]

Some useful background reading:

• How to build and push to GitHub's Package Registry with GitHub Actions
• Example of building multiple Docker images in a monorepo
• Discussion of how to re-use Docker code in GitHub Actions workflows with the build matrix

[humphd]

@TDDR has done great work getting us to the point of being able to do this. However, I've discovered that the CDOT org isn't allowed to publish to the GitHub Package Registry

As I see it, our options are:

1. move Telescope to its own GitHub org that is totally open (no private repos). This is going to cause a bit of churn while we get all kinds of things set up again with automation, permissions, connected services, etc.
2. host our own Docker registry on staging/production

I don't think there is another (free) option. Docker Hub is not going to work for a Team, and Amazon ECR will cost.

What do people want to do? I think we have to move toward hosting our images. cc @manekenpix.

[sirinoks]

I'm moving the second part of this issue for 2.7. Looks like there are some decisions to be made.

[humphd]

I'll file a follow-up on what remains vs. holding this, since @TDDR's part is actually done and merged.

[humphd]

Filed #2801.