Layered-vscode, so hard to make it work with distroboxes. Can we make it reproducible

[f0nzie]

These two fixes should help to write the vscode to Distrobox, DevContainers integration in Silverblue derivatives:

DevContainers and layered-vscode - another bug [Solved]

Just “victorious” after fixing a problem between layered-vscode and Distrobox containers, went on to test DevContainers. It turns out, it crashes the DevContainer creation process when trying to create a new one from the templates in the menu. No, it’s not the added .json config file for a distrobox. The two problems are not related. Even so, I reverted the changes, rebooted with a fresh installation, and still the problem persists. The issue is present in Silverblue-40 as well as Bluefin-DX-39. …

Layered-vscode to distrobox integration - login as ${USER} - [Solved]

I think finally I got it cracked! I found a method to integrate layered-vscode to distrobox containers and logging as ${USER}, instead of root. The trick is on creating an exclusive .json configuration file for each of the distroboxes you plan to enter in for development. This vscode configuration file creation will not occur automatically; you will have to create the folder nameConfigs under ${HOME}/.config/Code/User/globalStorage/ms-vscode-remote.remote-containers/, and then drop your .jso…