anchor.diff:  docker run -d -p 8983:8983 --name my_solr solr solr-precreate gettingstarted
   ----
   
  -The `solr-precreate` command takes an optional extra argument to specify a configset directory below `/opt/solr/server/solr/configsets/`.
  -This allows you to specify your own config.
  -See https://github.com/docker-solr/docker-solr-examples/tree/master/custom-configset[this example].
  +The `solr-precreate` command takes an optional extra argument to specify a configset directory below `/opt/solr/server/solr/configsets/` or you can specify a full path to a custom configset inside the container:
  +
  +[source,bash]
  +----
  +docker run -d -p 8983:8983 --name my_solr -v $PWD/config/solr:/my_core_config/conf solr:8 solr-precreate my_core /my_core_config
  +----
  +
  +N.B. When specifying the full path to the configset, the actual core configuration should be located inside that directory in the `conf` directory.
  +See <<config-sets.adoc#,Configsets>> for details.
  +
  +==== Using solr-create Command
   
   The third option is to use the `solr-create` command.
   This runs a Solr in the background in the container, then uses the Solr control script to create the core, then stops the Solr server and restarts it in the foreground.
  
positive.code: On a non-Docker Solr, you would run the server in the background, then use the <<solr-control-script-reference.adoc#,Solr control script>> to create cores and load data.
  With Solr docker you have various options.
  
  The first is exactly the same: start Solr running in a container, then execute the control script manually in the same container:
  
  [source,bash]
  
negative.code: ----
  docker run -d -p 8983:8983 --name my_solr solr solr-create -c gettingstarted
  ----
  
  ==== Custom Set-Up Scripts
  
  Finally, you can run your own command-line and specify what to do, and even invoke mounted scripts.
  For example:
  