feat: add dx-specific user setup, install devcontainers/docker vscode extensions by default

[jeefy]

This sets up a fresh install of Bluefin to have VSCode set up to use a Distrobox container (via devcontainers)

There needs to be a shim in place to ensure you enter the distrobox container as the local user and not as root.

It does require Docker to be available on the host (which is a requirement of the devcontainers extension

Refs:
#726
https://universal-blue.discourse.group/t/should-we-really-recommend-vscode-podman-as-supported/220/13

[bketelsen]

Is there a place to document how to specify the distrobox container in the devcontainer configs?

[jeefy]

Is there a place to document how to specify the distrobox container in the devcontainer configs?

There may be, but I don't think that's something we should set by default. Since the lifecycle of the Distrobox container is outside of VSCode, we shouldn't make assumptions on what the container is named.

[p5]

This is great, although my only concern is this will try to install the VSCode extensions on all Bluefin images, whereas Bluefin DX is the only one where VSCode is installed.

Not sure what the best approach would be. I guess conditionally running the scripts based on the contents of IMAGE_INFO JSON file

[jeefy]

I guess conditionally running the scripts based on the contents of IMAGE_INFO JSON file

Good call @p5, updated the PR with that :)

[castrojo]

Any final comments on this one? I'd like to start testing this this weekend!

[m2Giles]

Would this break normal dev-containers forcing the use of distrobox due to the docker path being that shim?

[jeefy]

After talking with @castrojo a bit, this is the route we settled on. :) Does change the PR quite a bit but it simplifies it. 🙌

[KyleGospo]

Looks good, may want to increase the version at the top of the user setup to ensure this is run for everyone

[castrojo]

Will that clobber people's existing setups? I'm fine with it being new-install only so we don't interrupt people's existing flows.

[EyeCantCU]

Will that clobber people's existing setups? I'm fine with it being new-install only so we don't interrupt people's existing flows.

Unfortunately that's true. If this was its separate thing (I think it should be a separate service since it uses an internet connection to install those extensions) it wouldn't be an issue though

[castrojo]

Yeah can we do that @jeefy? Sorry to make this process longer than it needs to be. (On the plus side after this we're done!)

[EyeCantCU]

Left some comments regarding converting this over to a separate service and a couple other things

[jeefy]

All comments should be addressed.

If we add additional post-install config steps, we might want to figure out a better way to track what's run. A bunch of dot files in a home feelsbadman, but that's a problem for another PR. :)

[EyeCantCU]

All comments should be addressed.

If we add additional post-install config steps, we might want to figure out a better way to track what's run. A bunch of dot files in a home feelsbadman, but that's a problem for another PR. :)

Things are looking fantastic! Definitely up for handling this in a better way. Having a lot of dotfiles is slightly annoying

[EyeCantCU]

One final thing - the Containerfile needs the service to be enabled: systemctl enable --global bluefin-dx-user-vscode.service

[EyeCantCU]

LGTM!