Skip to content
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

Open
coderpatros opened this issue Aug 31, 2020 · 6 comments
Open

Official Docker image #54

coderpatros opened this issue Aug 31, 2020 · 6 comments

Comments

@coderpatros
Copy link

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.

@nblumhardt
Copy link
Member

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! 👍

@coderpatros
Copy link
Author

Thanks @nblumhardt

@feitzi
Copy link

feitzi commented Mar 4, 2021

Is the docker image already on your backlog?
We definitely want to use that in our K8 Cluster to archive interruption-free Seq Updates and Pod movements, but we are not sure if it's the correct way with seq-forwarder because it seems is not in active development.

@nblumhardt
Copy link
Member

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 :-)

@dazinator
Copy link

Just chiming in to say, would really like a docker image for this.
Would it be possible to send the forwarder docker logs (e.g https://docs.datalust.co/docs/collecting-docker-container-logs) and have those forwarded? I am considering a scenario where the seq server is on different infrastructure to the docker swarm, so being able to buffer the logs at the forwarder will help provide better resiliency should the seq server go down for a period, or there be some type of transient network fault between the environments.

@nblumhardt
Copy link
Member

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!

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

4 participants