`ujust develop` but remove VSCode from packages?

Hello! I am trying to move from NixOS to Bluefin for my workstation and one thing that I discovered is that VSCode provided with ujust develop which is installed as a layered package as I understand does not work well with Distrobox. What happens is extension host does not work when attaching to distrobox container with podman-host script provided from the distrobox project. Flatpak VSCode runs fine and I was wondering if it is possible to get rid of RPM VSCode package manually?

Hi! Is there a reason non-dx Bluefin (run ujust devmode again) doesn’t work? That’ll remove the layers, and you can Flatpak in whatever you need?

My workstation is not only desktop and also a host for my media server, Forgejo instance and other things so I am still using Docker for compose files and without development mode that is not available and I have to layer it on my own, or am I wrong?

1 Like

I am not really following the ask.

But, VSCode works well with Docker (rather than podman).

See the experiments I did here:

Experiments 1 & 2 are pertinent to this discussion (I think).

You’re right - for your use case it sounds like DX is correct with you if you need docker. Above post by @klmcw may help you further!

Or else you can install VSCode as a flatpak too. Just set the flatpak version to be the default. You can override the system default by creating a user-override ~/.config/mimeapps.list. I really like Arch’s wiki for those things:

mimeapps.list - XDG MIME Applications - ArchWiki

You could also use Files (Nautilus) to change the file type associations, but then I think you could not distinguish between both VSCode’s. When editing the mimeapps.list, you associate file types to applications’ .desktop files so it’s easier to make sure the flatpak VS Code is first in priority.

I am still not understanding the problem attempting to be solved here.

I did use the VS Code flatpak on Fedora WS up to 40. But I was not using devcontainers then.

I am not sure what the reason was but vscode was placed in the bootc image for a specific reason. Good question to ask j0rge.