We hope you are enjoying Docker and look forward to hearing your feedback. Whether you want to raise a bug report, a feature request or just request a correction to something, we really value our community input.
We do ask that you read this document and send us any issues or raise pull requests to make sure we understand clearly what you are asking for. This will help ensure we are making the right decisions and taking the right actions.
You are very welcome to create new issues on this project to request new features in any of Docker products.
If you would like to suggest a new feature, we ask that you please use our issue template. This contains a few essential questions that help us understand the problem you are looking to solve and how you think your recommendation will address it. We also tag incoming issues from this template with "community_new". This lets our teams quickly see what has been raised and better address the community recommendations.
To see what has already been proposed by the community you can look here.
We would ask that you please don't use this repo to raise bugs. Each of our products has it's own repo where issues relating to that product are raised. We have chosen to do this as our products are all quite different, and as a result we need quite different information for each product to best understand how to help you.
To raise a bug please use:
Security issue notifications
Please do not create a public github issue. If you discover a potential security issue in this project we ask that you notify Docker Security send your report privately to email@example.com. Please do not create a public github issue.
See the LICENSE file for our project's licensing. We will ask you to confirm the licensing of your contribution.
We may ask you to sign a Contributor License Agreement (CLA) for larger changes.