logspout
logspout copied to clipboard
gliderlabs
supporting containerd directly? (Feature request)
Hello
We use logspout in our docker infrastructure. Now we are planning to switch to kubernetes based on containerd. Kubernetes doesn't support dockerd anymore in the future.
Is there a plan to migrate/enhance logspout to this? Thanks
Due to lack of development time, this project has pretty much gone into maintenance mode. However, I am certainly open to guiding and reviewing a PR to achieve this goal.
We use logspout and like it in part b/c of its smaller resource footprint compared to other things out there. Would you be able to please suggest any spiritually similar alternatives?
@merowing1279 please by all means feel free to take this. let me know if i can offer any insight or assistance
ok :) what I'm understanding here is to use instead of docker socket the containerd socket and asking about log the containerd API. Am I right?
sounds right to me? we also need to sort out how we will test and (maybe?) potentially fallback to the previous functionality. if we don't want to do that then we at least need to document the bare minimum docker/containerd version we support after this change.
I'm thinking to have the both working version. I will try to prepare a good interface for hiding the type of runtime implementation which is using during starting the logspout.
No we don't need this feature anymore. We switched to filebeat from elastic
@merowing1279 did you make any progress on this? We are considering the switch to containerd and currently use a derivative of this container.
@karlvr you can go with containerd.
Do you mean that the current logspout version works with containerd as well? Or do we need a special version of it? Could you elaborate a bit more? Thanks!
