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?

  • What are the security and performance constraints of using docker containers in a RESTful API in order to execute untrusted code?
  • Get python project into docker image
  • Citrus-Framework: How to wait for container to be healthy?
  • docker connect from container to public ip of host
  • Don't understand why my Docker image is not being saved
  • Adding NPM and Bower to a Dockerize LAMP environment
  • What is content of X-Registry-Auth for Docker push to private registry
  • The command '/bin/sh -c returned a non-zero code: 127
  • Docker Toolbox - Localhost not working
  • Journalctl : add _SYSTEMD_UNIT field into log printout
  • How can I map a docker volume to a google compute engine persistent disk
  • Using Docker compose within Google App Engine
  • 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.