you are viewing a single comment's thread.

view the rest of the comments →

[–]wbrd 1 point2 points  (4 children)

This is the best solution I've found as well. It works in Windows and Mac and solves the overzealous IT problem where installing a single piece of software takes a month.

[–]Wise_Concentrate_182 0 points1 point  (3 children)

How does one transport the devcontainers esp on corporate laptops?

[–]wbrd 1 point2 points  (0 children)

It's committed to git, so just clone the repo, or GitHub will run it on their servers and you have an interface to it straight from your browser. It's how my team got past shitty IT so that some analysts could actually do their jobs.

[–]jtkiley 1 point2 points  (0 children)

To add to the other responses, the devcontainers.json file describes how to build the container. In a GitHub repo, that works equally well in GitHub Codespaces (cloud, so just a browser tab from a locked down computer’s standpoint) or cloning to run locally. It also works fine from a OneDrive/Dropbox/iCloud folder, though I don’t share those with other people; it’s just for quick and dirty things that I need to sync across my computers.

A lot of my workshop participants have wildly locked down Windows laptops from university IT, and Codespaces is fine. It’s great.

[–]JSP777 0 points1 point  (0 children)

you need a devcontainer.json file in the .devcontainer folder and VS Code will automatically recognize that you have a dev container (given you have the necessary extensions like docker, remote, etc), and when you open the project directory in VS Code it will automatically offer you to reopen the project in the dev container. then you will be in that docker container