Live data from Hacker News

VSCode, Dev Containers and Docker

blog.feabhas.com

231–234 of 234 posts

Re: VSCode, Dev Containers and Docker

#231

I'm not quite sure that I understand the advantages of doing development work inside of the container. What am I missing?

If you work in enterprise 80% of developers have to rock windows laptops for compliance reasons but develop applications that will run on redhat/centos in the end.

Re: VSCode, Dev Containers and Docker

#232
post #191

Earlier quoted context omitted.

On Windows Docker runs in a VM.

That's wrong: "With the latest version of Windows 10 (or 10 Server) and the beta of Docker for Windows, there's native Linux Container support on Windows. That means there's no Virtual Machine or Hyper-V involved (unless you want), so Linux Containers run on Windows itself using Windows 10's built in container support". In any case, as Linux and macOS prove, there's no need for docker to have to run on a VM. And it s…

You’re quoting a random blog post from Scott Hanselman and not Docker release notes.

I don’t know what happened with that but I was not wrong and Docker for Windows does still run in a VM: https://docs.docker.com/docker-for-windows/install/

I assume you don’t use Docker on Windows and just pasted the first google result?

Re: VSCode, Dev Containers and Docker

#233

Earlier quoted context omitted.

Let's say you maintain or occasionally code several big webapps in Ruby. One uses Ruby 2.4 and Ruby-on-Rails 3.2, another uses Ruby 2.6 and Ruby-on-Rails 5.2, and the last one is bleeding edge using Ruby 3.0 and Rails 6.1 Having all versions of you language and framework installed top level is a huge pain in the ass, since they inevitably will interfere with each other. Having separate containers with all necessary d…

rbenv actually solves this quite well. You can set a project-level version in a .ruby-version file, and each lang version has its own gem cache

I work with several programming languages, its easier to make the problem language agnostic.

Re: VSCode, Dev Containers and Docker

#234

Earlier quoted context omitted.

Can only second this, we use a VSCode devContainer-based setup in all of our projects and even migrate our legacy projects to it (software agency). Here's our current base go template, you only need Docker+VSCode on your system to get started: https://github.com/allaboutapps/go-starter Bonus points: * As all IDE operations solely run within the local Docker container, all developers can expect that their IDE will wor…

Does that force everyone to use VS Code only? Can non VS Code developers also work efficiently?

yep, currently it forces our engineers to use VS Code or a terminal-based setup (or GitHub Codespaces). Hopefully Goland / IntelliJ catches up in this year...
Post reply on HN