cli icon indicating copy to clipboard operation
cli copied to clipboard

Mise ... vs Dev Container Environment setup

Open Konfekt opened this issue 3 months ago • 3 comments

Hello, would it make sense to explain in a paragraph to an outsider when a dev container is to be preferred to using Mise (or its predecessors like asdf) to set up a dev environment and vice versa? For example, under Microsoft Windows, the dev environment likely has to be used inside WSL with a container?

Konfekt avatar Oct 10 '25 18:10 Konfekt

For example, I found

The main point of devcontainers in my eyes is that you have everything you need in BUILD containers, and then you well, put your DEV TOOLING in DEV containers. Which means that developers with different workflows can and should be able to get different customizations which integrate seamlessly with the container. ... Devcontainers are basically just a wrapper around docker and postinstall shell scripts

Konfekt avatar Oct 10 '25 18:10 Konfekt

Hi @Konfekt, Thank you for reaching out! If you're interested in using Mise within a dev container, there's a dedicated feature available for that. Please refer to the official documentation for more details.ref.

Thanks, Sireesha

sireeshajonnalagadda avatar Oct 30 '25 06:10 sireeshajonnalagadda

Thank you for your reply; question was rather to which extent they are interchangeable, using Mise with a Dev container seems rather redundant; for example, a comparison to which extent, and how, a Windows mise set-up can be replaced by a dev container.

I imagined container to refer to a docker (pod) container, which is rather a Linux concept, as Windows suffers less from glibc incompatibilities, say. So my naive guess was that a Windows Dev container assumes the use of WSL to be run inside it (which might be unavailable on an administered work machine). Just basic use(fulness), especially under Window.

Konfekt avatar Oct 30 '25 07:10 Konfekt