Noting jenkins.install.UpgradeWizard.state

README.md

@@ -163,6 +163,8 @@ In case you *do* want to override, append '.override' to the name of the referen
 
 Also see [JENKINS-24986](https://issues.jenkins-ci.org/browse/JENKINS-24986)
 
+## Preinstalling plugins
+
 For your convenience, you also can use a plain text file to define plugins to be installed
 (using core-support plugin format).
 All plugins need to be listed in the form `pluginID:version` as there is no transitive dependency resolution.
@@ -198,6 +200,14 @@ script-security:1.13
 ...
 ```
 
+For 2.x-derived images, you may also want to
+
+    RUN echo 2.0 > /usr/share/jenkins/ref/jenkins.install.UpgradeWizard.state
+
+to indicate that this Jenkins installation is fully configured.
+Otherwise a banner will appear prompting the user to install additional plugins,
+which may be inappropriate.
+
 # Upgrading
 
 All the data needed is in the /var/jenkins_home directory - so depending on how you manage that - depends on how you upgrade. Generally - you can copy it out - and then "docker pull" the image again - and you will have the latest LTS - you can then start up with -v pointing to that data (/var/jenkins_home) and everything will be as you left it.