gelf driver doesn't work

[dzirg44]

• [x] I have tried with the latest version of my channel (Stable)
• [x] I have uploaded Diagnostics
• Diagnostics ID: ACA97E73-1FC1-48C4-BDB2-582B72FF82ED/20190824114547

Expected behavior

• sending logs via gelf driver to the logstash container

  Actual behavior

  • nothing happens

    Information

    Docker for Mac: 2.1.0.1 (stable)
    

    Steps to reproduce the behavior

    1. write simple docker-compose.yml file

       
       version: "3"

    services: logstash: image: docker.elastic.co/logstash/logstash-oss:7.1.1 ports:

    • 12201:12201/udp volumes:
    • ./logstash.conf:/usr/share/logstash/pipeline/logstash.conf:ro networks:

    • logging-network

      httpd: image: httpd:latest depends_on:

    • logstash ports:
    • 8033:80 logging: driver: gelf options: gelf-address: "udp://0.0.0.0:12201" tag: "http" networks:
    • logging-network

    networks: logging-network: driver: bridge

      2. put into this directory `logstash.conf` file
    ```js
    input {
      gelf {}
    }
    
    output {
      stdout {
        codec => rubydebug
      }
    }

    3. start with command

       docker-compose up

    4. use curl

       curl http://0.0.0.0:8033

[chriszwickerocteris]

I have the same (or a similar) issue. I've got a running ELK stack and I can manually send gelf logs to it. Whatever I do to set up a docker container to log to it via gelf, thought, it fails.

[ViXP]

I have the same issue. When I'm running the same docker-compose file on docker-machine - I have no problems with gelf driver. On Docker Desktop it is simply does not send anything. When I'm using host networking mode - it starts working with 127.0.0.1, but then I need to use host networking for whole ELK stack, so they'll be able to call each other, and it is not variant for me.

[powerc9000]

Is there any update on this? I have been trying to setup graylog logging and nothing has worked. Very frustrating.

[docker-robott]

Issues go stale after 90d of inactivity. Mark the issue as fresh with /remove-lifecycle stale comment. Stale issues will be closed after an additional 30d of inactivity.

Prevent issues from auto-closing with an /lifecycle frozen comment.

If this issue is safe to close now please do so.

Send feedback to Docker Community Slack channels #docker-for-mac or #docker-for-windows. /lifecycle stale

[dzirg44]

/lifecycle frozen