-
Notifications
You must be signed in to change notification settings - Fork 375
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Feature: publish official docker images #674
Comments
We have a Dockerfile, if someone'd like to turn that into an official image then please send some PRs to build one in the GitHub Actions workflow as part of |
Hi @jaqx0r , I would like to take this issue. As i can see we already have a dockerfile and we need to set up a docker image with github actions so that it pushes it after every release?. Can we push the registry to Google Container Registry (GCR)? |
Go for it, send me some PRs :D
…On Sun, 1 Jan 2023 at 20:37, Karanjot Singh ***@***.***> wrote:
Hi @jaqx0r <https://github.com/jaqx0r> , I would like to take this issue.
As i can see we already have a dockerfile and we need to set up a docker
image with github actions so that it pushes it after every release?. Can we
push the registry to Google Container Registry (GCR)?
( btw happy new year 🎉 )
—
Reply to this email directly, view it on GitHub
<#674 (comment)>, or
unsubscribe
<https://github.com/notifications/unsubscribe-auth/AAXFX66TPGB3O47TN6T6JBTWQFF6XANCNFSM56CEWJZQ>
.
You are receiving this because you were mentioned.Message ID:
***@***.***>
|
is there any progress? |
I have created #710 to build and push a docker image to the GitHub Container Registry since this allows us to use the builtin GITHUB_TOKEN for authentication. I followed the Github Actions Docs closely to achieve this. |
Currently there is no official docker image being published for mtail. A typical use case is running mtail next to an application as a sidecar to parse logs and publish the metrics.
It would be great to just use an upstream docker image that matches each version published and avoid setting up custom build pipelines. As this can be official images, build instructions as well as integrity can be ensured.
The text was updated successfully, but these errors were encountered: