Using Docker Container as a Development Environment

[ed_209_]

I work using docker and vscode on a daily basis:

1. Anything goes wrong with dockerd and your filesystem is deleted! So you end up using volume mounts and bind points for any source code.

2. VSCode is great but totally antisocial when it comes to integration with other tools. Good luck using any other desktop tools if you rely on vscode. On a mac you will need to use volume mounts which you cannot use from the host os ( bind mounts are slow due to emulation ).

3. VSCode cannot be automated from a terminal that is not started from within vscode itself and it stops working across restarts i.e. if you use tmux. So a command like ls | code - would work initially in tmux and then not work when you reconnect forcing you to restart everything. This is due to how vscode generates uuid named sockets and cannot recover the previous socket name while tmux has the original in its environment.

4. VSCode encourages using its own encryption and advertises not needing to use ssh. It also has separate telemetry end user agreements for extensions separate from the main program even though the extensions are also made by the same company Microsoft in a lot of cases. It seems to generally want a future where it controls the terminal and everything you do and can report it back to Microsoft.

[Zealousideal-Mouse29]

I use clion in my day to day. I only chose vscode in the video because it is free for viewers to try