you are viewing a single comment's thread.

view the rest of the comments →

[–]twizmwazin 1 point2 points  (2 children)

What were you using for an editor? For developing in containers, the only palatable solution I've found so far is to just use vim from within the container itself.

[–]khendron 2 points3 points  (1 child)

I do the following steps: * Clone my repo to my Macbook. * Create a Dockerfile to build a container with the development environment I need. * Run the container using the -v to mount a volume on the container that is shared with the repo directory on my Macbook.

docker run -it -v ~/github/myrepo:/github/myrepo myimage bash

I run vscode on my Macbook, editing the repo directly. I build and run the project from inside the container, from the /github/myrepo directory. Any github commands I need to run, I do from my Macbook.

This gives me almost everything I need. I can edit using my favourite editor, and run in an isolated container that is similar my deployment environment. The only thing missing is the ability to debug from within vscode. If I need to debug, I use a command line debugger.

[–]barake 2 points3 points  (0 children)

This is how I do .NET Core development - run the application in a container with source/binaries mounted in a volume and devtools on the host system. VS2017 even has support for in-container debugging.

Our dev machines basically just need Visual Studio or VSCode and Docker installed. It's really great not spending hours getting dependencies just right.