We would love practical, unique, and inspiring samples to help developers tailor their own Dockerfiles to suit their needs.
- All contributions must install Visual Studio Build Tools.
- All contributions must be text (dockerfiles, scripts, etc.).
- All contributions must adopt the MIT license in the root of this project with accompanied header (see example).
- All contributions must be in a unique directory.
- All contributions must have a README file explaining in generalized terms (i.e. no company secrets, but providing context on who you are or represents is optional and might be useful) what sort of workloads the Dockerfile supports (see example).
- All supporting files referenced within the Dockerfile must be text and included within the samples directory (see example).
- All contributions must be tested and work if someone were to copy the files and run commands as described in your README.
- All contributions must be easy to understand and must not be obfuscated. These are samples, and we want end users to be confident should they use these samples as a starting point for their pipeline.
- Include a link to your README file in the root README sorted by its brief title.
Please consider the .NET Framework + native desktop sample a template and author yours similarly.
The rules above will be enforced in pull request reviews and you may be asked to make changes. PRs that have not been fixed within 2 weeks may be abandoned. You can still make requested changes and re-submit at any time.
Contributors are encouraged to derive new, tested samples that provide significant value. If you believe you have found a problem, please open a new issue and @tag the author of the sample. Since all these samples should be tested, the author's feedback will be vital during the review process.