Works most of the time with WSL2 but containers PRESSING F1 and "peacock" gives only peacock documentation?

[KonanTheLibrarian]

Versions:

• OS: Windows 10 Enterprise WSL2 with Debian, bug in Docker Container with Debian (all latest) Docker version 24.0.5, build ced0996
• VS Code version 1.80.1
• Peacock Version v4.2.2
• Using Docker version 24.0.5, build ced0996 without Docker Desktop.
• Not using Docker Desktop as it is not needed, it is not Docker but a wrapper for it, it is not reliable, it looses sync, it tries to start WSL2 at bootup causing system failures, it was found to contain a half finished paywall which was obviously planned and the "experimental features" in the Docker Desktop settings area turned out to be spyware. People are not amused at this!
  All the Docker features and more are covered by VS CODE Extensions with real Docker installed. Don't use Docker Desktop it is NOT Docker and is a mountain of bugs right in the design, not just the implementation.

Describe the bug
Peacock with Ctrl+Shift+P and "peacock" shows only documentation. Annoying can't change colour.

Solution at a Guess
This guy willpower232 . Says that you have to press the Folder icon and then it will transfer peacock metadata to a file. My take on this is without the user choosing project folder, the metadata can't stick so colours can't be chosen yet. (But Colour should reside in memory - and wait for folders to exist). So the fix will be easy to implement using a temporary location that transfers settings once the user as finally "chosen the base folder for VSCODE in a new VSCODE project instance". Obviously ask the user to chose a folder when they are choosing a colour!!!!

To Reproduce
Steps to reproduce the behavior:

1. Launch a container with Linux in it eg Debian:Latest
2. In WSL VS CODE press Docker whale icon.
3. Select your running container and launch it with seperate new, and it's own VSCODE instance.
4. Press F1 and type peacock
5. See annoying Peackock Documentation only!
6. Press Extensions icon and find Peacock already installed.
7. Not tried uninstalling peacock and reinstalling it (in the container).

Expected behavior
Normally F1 gives peacock and the colour favourites.

Screenshots
If applicable, add screenshots to help explain your problem.

Additional context
Problem is long running.

[johnpapa]

Thank you @KonanTheLibrarian for creating this issue!

[willpower232]

Is this the issue where you have to open a folder of code first before you can change any peacock settings because it writes the colours to a local file?

[KonanTheLibrarian]

You're Welcome! Peacock is one of the most brilliant plugins for users who run both VSCODE and Windows in dark mode - can't see the edges of windows and with 10 VSCODE instances can't tell which one is which. Peacock solves it with nice colours and you don't have to be gxy to use it ;-) My bet is this developer will be able to fix this in 1 hour as the full features are failing to shift across and stick to all instances of VS CODE ... eg Docker VSCODE separate instances.

• IN CONTRAST: Compared to the "IP gone missing in WSL2" those in charge of the bugs close thousands of the same bug reports STRETCHING back 13 years! UNFIXED! COSTING MICROSOFT SOME 2 BILLION IF NOT, MORE - WSL2 IP Vanished problems still not fixed. Can't ping or DNS resolve an internet address in WSL2 hell you're on your own! I was the only one who went ballistic on this and got away with it as I know 30+ key staff supporting companies bigger than Microsoft Other people just got censored for saying HOW BAD MISSING IP on WSL2 has got! 20 different work-around solutions exist none of which work fully! WSL2 team FIX THE IP PROBLEM, all other Windows apps work on the network, JUST NOT WSL2!

[KonanTheLibrarian]

Work around from this guy willpower232 . Says that you have to press the Folder icon and then it will transfer peacock metadata to a file. Without the user choosing project folder, the metadata can't stick so colours can't be chosen yet. (But Colour should reside in memory - and wait for folders to exist). If you chose a base folder for the new project then F1 and typing "peacock" works. So the fix will be easy to implement using a temporary shared location that transfers settings once the user as finally "chosen the base folder for VSCODE in a new VSCODE project instance".