• To run VS Code, run bin/code.
• To run JetBrains Rider, run bin/rider.
• To use the dotnet toolchain run bin/dotnet.

Doing any of the above will pull a prebuilt docker image and run it. The processes for that particular item will be 100% isolated in a docker container, but it will have access to all of your files and X Forwarding (only for code and rider will show you a GUI).

Under ./bin there are some simple bash scripts that build and execute docker run commands for each container. You may either copy these scripts into a location that is on your PATH or you may add the ./bin folder to your path.

With this container and the included run script ./bin/dotnet you can execute the dotnet toolchain as if it was installed onto your local host system.

This container extends the offical microsoft/dotnet container and sets up su-exec to execute a given command as the same user as your host such that generated files will have the correct ownership, etc.

This container extends justinvanwinkle/dotnet and only serves as the base image for others. It installs a bunch of X server stuff, Mono, NodeJs, TypeScript, etc.

Run this with the included run script: ./bin/rider.

This container extends justinvanwinkle/dotnet-ide and installs JetBrain's Rider IDE.

Run this with the included run script: ./bin/code.

This container extends justinvanwinkle/dotnet-ide and adds Microsoft's Visual Studio Code Editor.

• Your working directory must be with-in your host users home directory. Attempting run any of the containers outside of this will result in failure.