logspout icon indicating copy to clipboard operation
logspout copied to clipboard

Log routing for Docker container logs

Results 111 logspout issues
Sort by recently updated
recently updated
newest added

Judging from the left side of the picture, these log messages are not sent together, **sent line by line** ![image](https://user-images.githubusercontent.com/18710659/91438152-7d6c9900-e89d-11ea-8645-12e25612fe7c.png) #### configuration information ``` docker run -d --name="logspout" --volume=/var/run/docker.sock:/var/run/docker.sock \...

Hello, I have tried to follow the README on Docker Desktop for Windows, but the build failed: PS C:\dev\GIT> docker build --build-arg LOGSPOUT_VERSION=master -t mycustomlogspout . unable to prepare context:...

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...

I have a docker-compose.yml file which starts logspout container and other containers in my application. On `doing docker-compose up`, in some cases log files are not getting created for some...

It would be great if logspout could ship logs to the local host syslog, rather than just remote syslog, without having to have a UDP or TCP listener on the...

type: enhancement

Hello there, I use logspout in docker cloud where I have multiple app containers in the single server. However logspout sometimes stops sending logs to cloudwatch for some of them....

Hi I'm trying to send logs on remote machine using raw adapter. On my log machine im using ELK (logstash). I have received container name in go template but i...

`ONBUILD` kinda sucks if it requires adding files that don't exist. Would be great if we could avoid onbuild completely for a non-custom logspout version :)

I use logspout 3.2.13 in k8s. And it's stoped logging after logrotate (with copytruncate) I read issue about it and enable INACTIVITY_TIMEOUT=1m But it didn't help. Does it exists any...

` websocket.Handler.ServeHTTP` serves to browser requests and was also causing logspout to crash when accessed by a client like `wscat` as they don't typically set the origin header (See https://github.com/gliderlabs/logspout/issues/412)....