[LOGS]: on windows, logs do not show up / are extremely slow?

[apostasie]

Description

TestLogsWithFailingContainer has been failing repeatedly on windows (for eg in #4209 )

What this test does is:

nerdctl run --name foo busybox sh -euxc "echo foo; echo bar; exit 42; echo baz"

Then:

sleep 5

Still:

nerdctl logs foo

will very often return nothing.

5 seconds feels like a very long time - even in a highly parallel context.

Also, this does not happen on linux.

There seem to be something different with Windows, where logs take much longer to show up.
Note that this also happen on other tests.

@fahedouch are we missing sync on windows, or something like that?

Any idea why windows would be different?

Steps to reproduce the issue

Describe the results you received and expected

na

What version of nerdctl are you using?

main

Are you using a variant of nerdctl? (e.g., Rancher Desktop)

None

Host information

No response

[apostasie]

This is also happening on TestLogsOutStreamsSeparated (and probably just any log test for windows).

Note that none of it is about waiting for a container started with -d.
All these failures are containers running and finishing in one command, with seemingly nothing in the logs.