Eric Swanson

> **Is your feature request related to a problem? Please describe.** `docker-compose` support a `--project-directory` argument that can be quite useful in conjunction with `-f`. Documentation can be found here:...

I've traced this issue to the file "C:\Program Files\nodejs\yarn". Does anyone know if this file is created by `corepack`, `nvm`, or even `yarn` itself? I couldn't find the original source...

It appears there was a patch made under the ["MINGW-packages" repository on July 30, 2023](https://github.com/msys2/MINGW-packages/blob/e8da4a221541efbf8cc280cd01a7db43ec9f3b03/mingw-w64-nodejs/0013-Revert-to-FHS-installation-paths-on-Windows-tests-no.patch#L327C34-L327C34). However, running `corepack enable yarn` replaces that manually edited local file with the unpatched version....

I just came across the `docker-compose watch` command in [a dev.to article](https://dev.to/code42cate/say-goodbye-to-docker-volumes-j9l) and the `podman-compose` documentation wasn't clear this command was not supported (which might be clear?). It would be...

This is a bit of a hack work-around. Because I have `docker` setup as an alias to `podman`, I was able to sniff the command support and change the network...

> Thanks for the solution @shanduur, it seems to solve the same issue I was facing. > > Additional question: would it be possible to specify the `--default-network` parameter in...

> This is not an error just a warning, Azure SDK auto instrumentation should be functional even if the warning is triggered, please ignore for now, this warning would be...

Thank you @hectorhdzg . It seems it is not possible to override the logging in the usual way. I was surprised that the "@azure/monitor-opentelemetry" package has it's own [`InternalAzureLogger`](https://github.com/Azure/azure-sdk-for-js/blob/648c9572c441fc7715cb89a623d7a05605c75e64/sdk/monitor/monitor-opentelemetry/src/shared/logging/internal.ts#L18) and...

Given the current limitations of the "@azure/opentelemetry-instrumentation-azure-sdk" logging, I was able to workaround this issue with a fairly significant flaw that logging details will be treated very differently for this...

> @ericis I'm a little bit confused about what is your specific need, we do in fact have multiple loggers involved, as we use both OpenTelemetry and Azure SDK packages...