-
Notifications
You must be signed in to change notification settings - Fork 16
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
Official Docker image #54
Comments
Hi Patrick! Definitely on the radar but we probably won't get this implemented/automated for a little while; I have a few more TODOs in mind that I'd like to do first, like environment variable-based config... I'd better raise a few issues :-) Will leave this open to track - thanks! 👍 |
Thanks @nblumhardt |
Is the docker image already on your backlog? |
Thanks for sending a note @feitzi; it's definitely our intention to maintain Seq Forwarder and develop it further. I've been hoping for some feedback on v2 before we move forward with it, but, I think it's probably time we just ploughed ahead :-) It should quite straightforward to put together the Docker image now that the prerequisites are all sorted. I'll merge #53 and let's take it from there :-) |
Just chiming in to say, would really like a docker image for this. |
Thanks for the nudge @dazinator. Still keen to do this but as yet unscheduled. The Docker log collection instructions you linked use GELF as the transport, which seq-forwarder doesn't support, so you may need a different solution there (Fluent Bit supports a wide range of input protocols, can buffer to disk, and can easily forward to Seq using an output config like the one in https://blog.datalust.co/tailing-a-log-file-or-folder-with-fluent-bit-and-seq/). HTH! |
Hi team!
Any current plans to create a docker image for this? Just don't want to go to the trouble of creating one if you are already working on it.
The text was updated successfully, but these errors were encountered: