Developing inside a virtual machine

Re:Developing inside a virtual machine by moritonal on Wednesday January 01, 2025 @05:07PM (#42569722)

Thr Dev Container ecosystem for VsCode really is quite impressive at the moment. All your dev dependencies, wrapped up in a docker image per repo.

[ Parent | on HN ]

Re:Developing inside a virtual machine by invalidname on Wednesday January 01, 2025 @10:32PM (#42571364)

100%. I've been using that and also the DevContainer support in IntelliJ/IDEA which is good but has some limitations (e.g. I can connect IntelliJ but not CLion at the same time).

[ Parent | on HN ]

Re:Developing inside a virtual machine by psyclobe on Thursday January 02, 2025 @02:19AM (#42572452)

Heh if you can work around ALL its weird quirks, especially on windows.

[ Parent | on HN ]

Re:Developing inside a virtual machine by elcritch on Thursday January 02, 2025 @07:10AM (#42573744)

Having supported team members where we were all running this setup there was constant fiddling with docker. Containers would freeze and often required restarting docker directly. Especially with WSL on windows.

It’s slick when it works.

[ Parent | on HN ]

Re:Developing inside a virtual machine by moritonal on Thursday January 02, 2025 @08:06AM (#42574074)

I noticed similar things, and found most these problems went away with more memory, and less usage of the "{}.features[]" in the `devcontainer.json` file.

[ Parent | on HN ]

Re:Developing inside a virtual machine by urronglol on Thursday January 02, 2025 @08:20AM (#42574165)

What quirks have you come across. The only annoyance for me was ssh agent having to uninstall the windows store version

[ Parent | on HN ]