[Windows] Fix tracing listener

[gabriel-samfira]

• The tracing socket is a named pipe on Windows
• Sets proper permissions on the named pipe
• Sets proper environment variables inside the executor
• Defines proper mount for the tracing socket

Signed-off-by: Gabriel Adrian Samfira gsamfira@cloudbasesolutions.com

[gabriel-samfira]

@tonistiigi I updated the PR. PTAL when you have some time.

[crazy-max]

Ah was going to say the unix:// protocol was missing redundant, good catch.

[gabriel-samfira]

Ah was going to say the unix:// protocol was missing, good catch.

Accidentally omitted the npipe:// variant on Windows when I moved code around. My eye twitched as I looked at that line, and didn't know why. 😄

[crazy-max]

Ah was going to say the unix:// protocol was missing, good catch.

Accidentally omitted the npipe:// variant on Windows when I moved code around. My eye twitched as I looked at that line, and didn't know why. 😄

Yeah this npipe:////./pipe/foo is confusing though.

[gabriel-samfira]

Ah was going to say the unix:// protocol was missing, good catch.

Accidentally omitted the npipe:// variant on Windows when I moved code around. My eye twitched as I looked at that line, and didn't know why. smile

Yeah this npipe:////./pipe/foo is confusing though.

You should see what it looks like when \ are used and go escapes them when they get printed 😄. But as funky as that looks, it is correct. Named pipes on Windows start with \\hostname\path\to\pipe. Where, if we're referencing the local host, a dot can be used instead of the hostname. Usernames are the same. You can use hostname\Administrator or .\Administrator. If you're loggin in as an AD user, that hostname can be replaced with the forest name.

Windows is fun sometimes 😄.