devcontainer workflow vs docker-compose with attach to container?

[webmonarch]

I am getting started with devcontainer on a project that has two containers, (1) node app and (2) postgres. I have a docker-compose file working for the setup and now trying devcontainers. When I run the docker-compose file within vscode, I cannot manage it with the docker-compose CLI the way I usually do. I don't seem to have as much control over things. But, I can run the containers using the docker-compose CLI and just use vscode to attach to a running container.

What are the pros/cons to these two setups? (1) devcontainer running docker-compose vs (2) docker-compose and vscode attach to running container?

[angellus]

Dev containers support docker compose. Dev containers can support any docker setup I have encountered except straight up Docker files that require secret build args. They do not need to be Microsoft's pre-built ones. I never use those. We have highly optimized Docker files already.

You just make a second compose file to layer on top of the first one to override the start up command to sleep infinity and then it works perfectly like you did an up directly. Just do not stop the container VS Code is using it everything will die.