Consuming Multiple Floating Licenses for Local Docker Development with IntelliJ?

Hi everyone,
I'm seeking clarification on using IntelliJ IDEA with floating licenses in a Docker container-based development environment.
Scenario:
Our team is considering using Docker containers as our primary development environment. This approach streamlines development by eliminating the need for individual software installations on developer machines. All dependencies, including open JDKs, Git, Git LFS, and application servers for various branches, would be packaged within the Docker image. We plan to access these containers remotely using the IntelliJ IDEA remote development plugin (https://www.jetbrains.com/remote-development/).
Question:
Does this scenario consume two floating licenses from our pool?
Here's our concern:
* We use Windows machines with WSL2 support running IntelliJ IDEA on the Windows side.
* Developers would connect to a local Docker container acting as the development environment via the remote development plugin.
* Upon connection, a new IntelliJ instance within the Docker container appears to request a separate license.
Based on the documentation regarding floating licenses (https://www.jetbrains.com/help/ide-services/floating-licenses.html) and remote development (https://www.jetbrains.com/remote-development/), it seems this setup might consume two licenses:
* One for the Windows-based IntelliJ IDEA instance with WSL2 support.
* Another for the IntelliJ instance opened remotely within the Docker container.
Sustainability and Licensing Concerns:
If this is the case, it could pose a sustainability and potential licensing issue. With each developer using this approach, the floating license pool could be depleted quickly compared to a native Windows development setup where only one license is consumed per developer.
Alternative Approach:
Given this potential double licensing situation, would installing a full version of IntelliJ IDEA directly within the Docker container and running it there be a more sustainable solution? This aligns with our past experience using a similar approach with Eclipse. While the user interface might not be as smooth as native Windows development, it remains usable and potentially faster. Modern WSL2 with native X11 support offers significant improvements compared to previous alternatives requiring additional X11 server tools.
Configuration Export:
Finally, if installing IntelliJ IDEA directly within Docker is the preferred approach, is there an easy way to export configurations from the Windows-based installation and import them into the Docker-based IntelliJ instance?
We appreciate any insights or guidance the community can offer on this topic.
Thanks,
Nuno