Yes I added it only for Windows because it is an edge case, even for Windows. It occurs when the actual directory URL is on a non standard port, so it needs to be specified. It would not happen on production, only during local tests.
So adding a migration path, or a backward compatibility, inside Certbot logic was too much here.
Instead I have some alternatives to develop Certbot for Linux on a Windows system:
- run a full Ubuntu inside VirtualBox, including the Docker engine. It will not be as fast as running Docker for Windows, but you will not get any limitations from the underlying system.
- use latest Windows (20.04) and enable the WSL2 engine in Docker for Windows. This is my current development stack, which gives both native performances and Linux full-compatibility.