microsoft / microsoft/windows-container-tools

How non entry point (random) process running inside Windows Container could write to docker default log output (stdout)?

Open
#15 3 comments 0 reactions 1 assignee View on GitHub

@iankingori is already working on this.

Since Jun 14, 2022.

enhancement
Dominant language
C++
Stars
277
Forks
77
PR merge metrics
No merged PRs in 30d

Description

Hi, first of all, thank's for this project. It's awesome to finally bring Windows Applications to container.

So, I have one Windows Container with various processes, .NET and Win32 legacy applications.

First scenario

Entry point calls myConfigurator.exe, who calls first.exe, who creates a pool of second.exe process

Second scenario

Entry point calls myConfigurator.exe, who calls ServiceMonitor.exe, who initialize my IIS ASP.NET Web Application, who creates a pool of second.exe process

Problem

I'm already using log4net appender to send all logs to elasticsearch, and it's all good.
But, I need to send logs to default docker log too, so datacenter operators can see logs the same way they do with standard/compliant containers, using docker logs, or portainer or any other container tool.

Question

  • How random processes running inside Windows Container could write to default log output?
  • How can I use LogMonitor to address those scenarios?

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.