Introduce a less opinionated Dev Container for devpod development?

[imphil]

#2 removed the original dev container config and build in https://github.com/skevetter/devpod/tree/main/.devcontainer and moved to a container in https://github.com/skevetter/devcontainers/tree/main/src/devpod. This container works, but I have two small problems with it:

• It's a rather opinionated setup. For example, it uses zsh by default and even sets a color scheme.
• It's unversioned and untied to the devpod repository itself, hence it cannot be easily changed together with code changes to the devpod repository (e.g., when bumping dependencies that also need to be present in the dev container).

While the current setup probably works great for you, @skevetter, it's a bit harder for other contributors to use. Would you be OK with me (re-) introducing a less opinionated container along with build support into this repository? (Looks like you got yourself into a situation where this isn't just a "fork for me" any more :-))

Customizations, including the installation of additional VS Code features, can still be done with VS Code settings that are then local to the user setup, and not shared with the whole project.

[skevetter]

Would you be OK with me (re-) introducing a less opinionated container along with build support into this repository

I support having a generic container image to facilitate ease of development across multiple contributors.

My requirements are:

• The image is made available as a prebuild (example https://github.com/skevetter/devcontainers/pkgs/container/devpod).
• Container changes go through a CI workflow.
• Features should be used in lieu of bespoke scripts/Dockerfile instructions when possible
• Specific profiles are allowed per the container resolution order https://containers.dev/implementors/spec/#devcontainerjson.

Nice to haves:

• Tests to validate container and features are installed correctly and files have the correct permissions.

Looks like you got yourself into a situation where this isn't just a "fork for me" any more

I have been running the same container workspace for devpod development for ~5 months now. It's extremely hacky at this point, but I'm keeping it alive for as long as I can. :)