Despite what I said above, one overly prescriptive idea I had would be to use Docker in Docker to spin up a mysql container alongside the devcontainer, given the recent enthusiasm for mysql.
I have started making an experimental fork on this which has the basic functionality of creating a template, but want to check if there’s any interest in this idea or if it’s a complete non-starter before taking it any further.
Initially, using it directly in VS Code results in a new VS Code setup without any extensions installed. I haven’t investigated thoroughly yet, but it’s likely that you can install specific extensions locally without including them in the devcontainers setup for all developers.
Utilizing Installing and working with the devcontainer CLI comes with several limitations. One example is that you cannot even run something like devcontainer down. I might be missing something due to a lack of knowledge, but I haven’t found a solution for this yet. Also, you do not have easy overview and management of your volumes, as you have with normal docker compose.
So fare, I was ending up twice to not work with devcontainers, as my usual setup is much better experience.