Run update.sh

Author: docker-library-bot

clojure/README.md

@@ -2,8 +2,8 @@
 
 -	[`latest`, `lein-2.7.1` (*Dockerfile*)](https://github.com/Quantisan/docker-clojure/blob/c77c13529de02183433da15e8227eba63cc96724/Dockerfile)
 -	[`onbuild`, `lein-2.7.1-onbuild` (*onbuild/Dockerfile*)](https://github.com/Quantisan/docker-clojure/blob/c77c13529de02183433da15e8227eba63cc96724/onbuild/Dockerfile)
--	[`alpine`, `lein-2.7.1-alpine` (*alpine/Dockerfile*)](https://github.com/Quantisan/docker-clojure/blob/c77c13529de02183433da15e8227eba63cc96724/alpine/Dockerfile)
--	[`alpine-onbuild`, `lein-2.7.1-alpine-onbuild` (*alpine-onbuild/Dockerfile*)](https://github.com/Quantisan/docker-clojure/blob/c77c13529de02183433da15e8227eba63cc96724/alpine-onbuild/Dockerfile)
+-	[`alpine`, `lein-2.7.1-alpine` (*alpine/Dockerfile*)](https://github.com/Quantisan/docker-clojure/blob/2a0ab08313a24effa5d7b93b1ced8204763e6628/alpine/Dockerfile)
+-	[`alpine-onbuild`, `lein-2.7.1-alpine-onbuild` (*alpine-onbuild/Dockerfile*)](https://github.com/Quantisan/docker-clojure/blob/2a0ab08313a24effa5d7b93b1ced8204763e6628/alpine-onbuild/Dockerfile)
 
 For more information about this image and its history, please see [the relevant manifest file (`library/clojure`)](https://github.com/docker-library/official-images/blob/master/library/clojure). This image is updated via [pull requests to the `docker-library/official-images` GitHub repo](https://github.com/docker-library/official-images/pulls?q=label%3Alibrary%2Fclojure).
 

consul/README.md

@@ -169,15 +169,15 @@ By default, Consul's DNS server is exposed on port 8600. Because this is cumbers
 Here's an example:
 
 ```console
-$ docker run -d --net=host -e 'CONSUL_ALLOW_PRIVILEGED_PORTS=' consul -dns-port=53
+$ docker run -d --net=host -e 'CONSUL_ALLOW_PRIVILEGED_PORTS=' consul -dns-port=53 -recursor=8.8.8.8
 ```
 
-If you are binding Consul's client interfaces to the host's loopback address, then you should be able to configure your host's `resolv.conf` to route DNS requests to Consul by including "127.0.0.1" as the primary DNS server. This would expose Consul's DNS to all applications running on the host, but due to Docker's built-in DNS server, you can't point to this directly from inside your containers; Docker will issue an error message if you attempt to do this. You must configure Consul to listen on a non-localhost address that is reachable from within other containers.
+This example also includes a recursor configuration that uses Google's DNS servers for non-Consul lookups. You may want to adjust this based on your particular DNS configuration. If you are binding Consul's client interfaces to the host's loopback address, then you should be able to configure your host's `resolv.conf` to route DNS requests to Consul by including "127.0.0.1" as the primary DNS server. This would expose Consul's DNS to all applications running on the host, but due to Docker's built-in DNS server, you can't point to this directly from inside your containers; Docker will issue an error message if you attempt to do this. You must configure Consul to listen on a non-localhost address that is reachable from within other containers.
 
 Once you bind Consul's client interfaces to the bridge or other network, you can use the `--dns` option in your *other containers* in order for them to use Consul's DNS server, mapped to port 53. Here's an example:
 
 ```console
-$ docker run -d --net=host -e 'CONSUL_ALLOW_PRIVILEGED_PORTS=' consul agent -dns-port=53 -bind=<bridge ip>
+$ docker run -d --net=host -e 'CONSUL_ALLOW_PRIVILEGED_PORTS=' consul agent -dns-port=53 -recursor=8.8.8.8 -bind=<bridge ip>
 ```
 
 Now start another container and point it at Consul's DNS, using the bridge address of the host:

eggdrop/README.md

@@ -36,7 +36,15 @@ After running the eggdrop container for the first time, the configuration file,
 $ docker run -i -e NICK=FooBot -e SERVER=irc.freenode.net -v /path/to/eggdrop/files:/home/eggdrop/eggdrop/data -d eggdrop
 ```
 
-Please note that, even in daemon mode, the -i flag for docker run is required.
+Please note that, even in daemon mode, the `-i` flag for `docker run` is required.
+
+## Adding scripts
+
+An easy way to add scripts would be to create a scripts directory on the host and mount it to `/home/eggdrop/eggdrop/data`. This would be accomplished by adding an option similar to
+
+	-v /path/to/host/scripts:/home/eggdrop/eggdrop/scripts
+
+to your docker run command line (and of course, don't forget to edit your configuration file to actually load it!)
 
 ## Exposing network ports