Closed matdehaast closed 2 years ago
@omertoast is going to handle this issue
If we're good with ghcr (vs docker hub), here's how Tigerbeetle images are being published for reference: https://github.com/coilhq/tigerbeetle/pull/38 https://github.com/coilhq/tigerbeetle/pull/40
Thanks for the recommendation, going with ghcr.
So, I tried to use Docker Build & Push Action to publish Docker images. But because the current Dockerfile is designed to only work with the yarn docker build plugin, the action fails when it's trying to build it using only the Dockerfile. There are two ways I can get the workflow done:
yarn docker build backend -t rafiki-backend
command and publishing it using Docker CLI.I think it's more reasonable to go with the first option, so I will be going with that one if no one is against it. I'm also open to any recommendations and comments.
Rafiki needs a mechanism to used tagged release that build docker images that are hosted on a container registery. All packages should be able to become a docker image as required. Ideally this should work through github actions