[imron]

> I always found docker as a dev environment rather painful.

I’ve found the following to work quite well:

Have a docker compose file setup that runs a container with all the necessary build tools and anything else.

Map home directories, /opt and anything else you want to persist as named volumes.

Run docker compose up -d

Use the remote development extension of vscode to connect to the container and develop almost as if it was local.

[davrosthedalek]

vscode's remote dev is indeed god-tier. I love vscode.

[imron]

I’m not a huge fan of vscode (speaking as a c++ dev), but remote dev is a killer feature so I use it over other alternatives.

[MathMonkeyMan]

This is a neat idea.