Description
Describe your feature request here
WSL 2 is functional for containers on self-hosted Windows agents with a clean install, despite lacking official support.
However, during agent upgrades, the bin directory is replaced with a symlink to the latest tools version. This breaks WSL 2 compatibility, as the Linux filesystem cannot mount symlinked directories. To work around this, we must manually replace the symlink with the actual bin folder after each upgrade. Automating this within the agent isn't feasible, as it cannot modify its own bin directory while running.
Ideally, the upgrade process would either preserve the original file structure or offer a configurable option to disable the symlink behavior.
Our use case relies on WSL 2 to run a Redis container required for emulating Azure services in integration tests.