Add devcontainer definition

[Krzysztof-Cieslak]

Having in the devcontainer definition in the workspace will make VSCode (if user has remote-containers extension installed) prompt user to open the workspace inside the defined docker container.
As you can see in the docker container we have .Net SDK 2.2, Node, Yarn, Paket and FAKE - i.e all our requirements.
VSCode will also automatically install the extensions specified in devcontainer.json. (inside container instance - i.e. not polluting host installation)

All this means users can start developing applications with VSCode and docker as only requirements - and they will automatically get full configure development environment with all dependencies installed.

[ghuntley]

stealing this, thanks :D

[ScottHutchinson]

# Install fake should be 	# Install paket

[Krzysztof-Cieslak]

# Install fake should be 	# Install paket

Thanks, fixed

[AndreasHassing]

You're not installing mono, are you?

[ScottHutchinson]

Title "Add devocntainer definition" should be "Add devcontainer definition"

[theimowski]

That's probably because the Remote - Containers extension is in preview version - wondering whether we should wait with that until it's in a stable version? I don't think many users have the insider version of VS Code installed (I didn't)

Then we could add an extension recommendation

[Krzysztof-Cieslak]

wondering whether we should wait with that until it's in a stable version?

TBF, I think we should merge this despite being insiders-only. (But I'm super excited about this feature)

If someone has insiders version then it is just added value.
If someone has stable then those are just 3 small files they can ignore. And, what's important, people will already have this definition in their repos when the feature will got released in stable. I.e. they'll be able to use it without any additional work.

And yes, we definitly should add extension recommendation.

[Nhowka]

I'm behind a corporate proxy and couldn't make it work. The dotnet tools were installed, but at the end it's trying to connect to my host machine name on port 80 and it's failing. Not sure what is trying to connect or what do I have to do...

Edit: That was the error on friday. Today I'm getting a different error:

SECURITY WARNING: You are building a Docker image from Windows against a non-Windows Docker host. All files and directories added to build context will have '-rwxr-xr-x' permissions. It is recommended to double check and reset permissions for sensitive files and directories.
Run: docker run -a STDOUT -a STDERR -p 127.0.0.1:8080:8080 -p 127.0.0.1:8085:8085 -v c:/Users/desmerio/BridgeChat:/workspaces/BridgeChat -v C:\Users\desmerio\.gitconfig:/root/.gitconfig -l vsch.quality=insider -l vsch.local.folder=c:\Users\desmerio\BridgeChat -l vsch.remote.devPort=9753 vsc-bridgechat-d072018bff7ceda88d9569e3f8fc4b3e /bin/sh -c echo Container started ;  while sleep 1; do :; done
C:\Program Files\Docker\Docker\Resources\bin\docker.exe: Error response from daemon: driver failed programming external connectivity on endpoint eager_brahmagupta (9aa56a5cacf821751939199d2d9d1f0807c427625e78a8d539b35450d37023bc): Error starting userland proxy: mkdir /port/tcp:127.0.0.1:8085:tcp:172.17.0.2:8085: input/output error.
Failed: Starting the development container
Command failed: C:\Program Files\Docker\Docker\Resources\bin\docker.exe run -a STDOUT -a STDERR -p 127.0.0.1:8080:8080 -p 127.0.0.1:8085:8085 -v c:/Users/desmerio/BridgeChat:/workspaces/BridgeChat -v C:\Users\desmerio\.gitconfig:/root/.gitconfig -l vsch.quality=insider -l vsch.local.folder=c:\Users\desmerio\BridgeChat -l vsch.remote.devPort=9753 vsc-bridgechat-d072018bff7ceda88d9569e3f8fc4b3e /bin/sh -c echo Container started ;  while sleep 1; do :; done

[theimowski]

Ok agreed.

Does the Debugger for Chrome extension needs to be installed locally or remotely? I can't seem to get it working using Debug SAFE app:

[theimowski]

Thanks @Krzysztof-Cieslak
When fable-compiler/webpack-config-template#11 is merged it should fix accessing the webpack dev-server