Explain limitations
@@ -13,10 +13,21 @@ This plugin requires Gradle >= 2.5 to work properly.
There are various benefits for using this plugin:
-1. Seamless integration with the build tool Gradle and its DSL
-2. Handles complicated communication logic between Docker client and daemon under the covers
-3. Simplifies the definition of complex workflows
-4. Minimizes build script setup logic by providing sensible conventions for different use cases
+1. Seamless integration with the build tool Gradle and its DSL.
+2. Handles complicated communication logic between Docker client and daemon under the covers.
+3. Simplifies the definition of complex workflows.
+4. Minimizes build script setup logic by providing sensible conventions for different use cases.
+
+=== Limitations
+
+The functionality of the plugin does not cover all possible use cases.
+Be aware of the following limitations:
+
+* A task type may not provide all possible options for the underlying Docker operation.
+Open an issue if you feel like it should be supported.
+* You cannot build multi-container applications via Docker Compose.
+The https://github.com/avast/gradle-docker-compose-plugin[Avast Docker Compose plugin] has proven to be a capable alternative.
+* Managing a Docker Swarm and/or Stack is not supported.
=== Further Readings
