Ledjon Behluli
Ledjon Behluli
This is due to an incorrect provided public key **format**.
Sure! What's the best way to go about it? Should I fork branch development or master?
Update I have not abandoned this! I have written HashiCorp if they could provide me a trial of Consul Enterprise, because I can't test without it. Waiting for a response...
Even with WSL 1.1.3 the latest image for sql-server 2022 doesn't work for me. As with others, 2019 does work! ``` WSL version: 1.1.3.0 Kernel version: 5.15.90.1 WSLg version: 1.0.49...
I can confirm that **upgrading to WSL 1.1.5** solved the issue with the **sql-server 2022** image, even while still being on Windows 11 **21H2**
@varminth have you considered memory streams?
@gfoidl please have a look again, thx!