You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm running fq in a container by building it based on the Dockerfile locally.
It would be neat to automatically publish container images for releases and something I'm tempted to work on.
This however raises a few questions I would like feedback on:
To where should the container images be published? Simplest way is probably Github packages, as secrets management and similar is automagically handled.
Where in the CI pipeline should images be built? GoReleaser has support to build and publish images, but it could be done using other Github actions as well.
Which architectures should the images be built for? Considering that the "runtime" image is based on scratch, it should only be a matter of support for cross-compiling the Go binaries.
The text was updated successfully, but these errors were encountered:
Sounds good! maybe start with just github packages registry for now?
About building i'm not sure, i would be nice to do via goreleaser but don't understand if it support multiple arch images or, it seems like not goreleaser/goreleaser#530. For what archs maybe the same archs that alpine build fq for? i wonder also if you could use the go cross building-abilities somehow?
Maybe do some github actions experiments in a forked repo?
I'm running fq in a container by building it based on the Dockerfile locally.
It would be neat to automatically publish container images for releases and something I'm tempted to work on.
This however raises a few questions I would like feedback on:
To where should the container images be published? Simplest way is probably Github packages, as secrets management and similar is automagically handled.
Where in the CI pipeline should images be built? GoReleaser has support to build and publish images, but it could be done using other Github actions as well.
Which architectures should the images be built for? Considering that the "runtime" image is based on scratch, it should only be a matter of support for cross-compiling the Go binaries.
The text was updated successfully, but these errors were encountered: