This repositories devcontainer setup deletes all your other devcontainers

[alcuadrado]

If you clone this repository in a devcontainer, it will delete all your other devcontainers.

This is extremely bad, as it ruins your development environment. This may not be as problematic for people who use this repository often, but it is for the casual contributor who uses devcontainer.

I don't know why docker system prune -f -a" was added as initializeCommand in #40825, but I think it should be removed.

(Sorry for not using an issue template. This is not related to node itself, but rather to its repository)

[mattaereal]

This is bad practice, the initializeCommand runs on your host machine.

From containers.dev documentation
initializeCommand:

A command string or list of command arguments to run on the host machine during initialization, including during container creation and on subsequent starts. The command may run more than once during a given session.

⚠️ The command is run wherever the source code is located on the host. For cloud services, this is in the cloud.

Note that the array syntax will execute the command without a shell. You can learn more about formatting string vs array vs object properties.

I don't know the specific reason why they do this but generally is due to the need to avoid polluting the docker system with new builds every time a new change is deployed. Nevertheless, this will undoubtedly destroy entirely all your other containers :/

Edited to fix a typo.

[RedYetiDev]

CC @bnb (Added the file)