GELF logging driver with Windows Containers

I’m trying get an ELK stack up (Elastic Search, Logstash and Kibana) and would like to get the GELF logging driver to forward events to Logstash, however whenever I run my container with the specified driver I get docker: Error response from daemon: logger: no log driver named 'gelf' is registered. even though I’m on 1.12.2-cs2-ws-beta. Is there a way to get this working on Windows Server 2016?

  • How to configure Debian SSHD for remote debugging in a Docker container?
  • So many Binlog_dump connections in Processlist?
  • Environment variables in docker when exec docker run
  • “CMD ['/home/user/']” in docker file doesn't work with docker-compose
  • boot2docker equivalent of docker exec
  • Conventional way to resolve docker derived image build time vs. image size tradeoff
  • Why is my Tutum service starting then within 2 seconds stopping with a container status “die” command?
  • Understanding Dockerfile CMD/ENTRYPOINT
  • What is the replacement for `--net=container` in new docker networking?
  • Docker container with Neo4j 2.3 enterprise edition exits without error message when mounting graph.db volume
  • Docker image with specific node version
  • How to set an environment variable in a running docker container
  • One Solution collect form web for “GELF logging driver with Windows Containers”

    The supported log drivers section does list GELF (Graylog Extended Log Format), but by default on docker for Linux (so within a Linux VM on other platforms)

    The official GELF documention does recommend in its installation page

    Some modern Linux distribution (Debian Linux, Ubuntu Linux, or CentOS recommended)

    So a Windows server 2016 might not include a Graylog server in its Docker.

    Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.