Run update.sh

jetty/README.md

@@ -1,9 +1,9 @@
 # Supported tags and respective `Dockerfile` links
 
--	[`9.3.10`, `9.3`, `9`, `9.3.10-jre8`, `9.3-jre8`, `9-jre8`, `latest`, `jre8` (*9.3-jre8/Dockerfile*)](https://github.com/appropriate/docker-jetty/blob/25ff3e0419721dd1812a49de72ee3aa37e41bbfd/9.3-jre8/Dockerfile)
--	[`9.3.10-alpine`, `9.3-alpine`, `9-alpine`, `9.3.10-jre8-alpine`, `9.3-jre8-alpine`, `9-jre8-alpine`, `alpine`, `jre8-alpine` (*9.3-jre8/alpine/Dockerfile*)](https://github.com/appropriate/docker-jetty/blob/25ff3e0419721dd1812a49de72ee3aa37e41bbfd/9.3-jre8/alpine/Dockerfile)
--	[`9.2.17`, `9.2`, `9.2.17-jre8`, `9.2-jre8` (*9.2-jre8/Dockerfile*)](https://github.com/appropriate/docker-jetty/blob/1ea4d8064136369ed2ec08fc5f4fbc3cae30c8d2/9.2-jre8/Dockerfile)
--	[`9.2.17-jre7`, `9.2-jre7`, `9-jre7`, `jre7` (*9.2-jre7/Dockerfile*)](https://github.com/appropriate/docker-jetty/blob/1ea4d8064136369ed2ec08fc5f4fbc3cae30c8d2/9.2-jre7/Dockerfile)
+-	[`9.3.10`, `9.3`, `9`, `9.3.10-jre8`, `9.3-jre8`, `9-jre8`, `latest`, `jre8` (*9.3-jre8/Dockerfile*)](https://github.com/appropriate/docker-jetty/blob/e399f08087f8efce4a272225e667c04a09a1996b/9.3-jre8/Dockerfile)
+-	[`9.3.10-alpine`, `9.3-alpine`, `9-alpine`, `9.3.10-jre8-alpine`, `9.3-jre8-alpine`, `9-jre8-alpine`, `alpine`, `jre8-alpine` (*9.3-jre8/alpine/Dockerfile*)](https://github.com/appropriate/docker-jetty/blob/e399f08087f8efce4a272225e667c04a09a1996b/9.3-jre8/alpine/Dockerfile)
+-	[`9.2.17`, `9.2`, `9.2.17-jre8`, `9.2-jre8` (*9.2-jre8/Dockerfile*)](https://github.com/appropriate/docker-jetty/blob/e399f08087f8efce4a272225e667c04a09a1996b/9.2-jre8/Dockerfile)
+-	[`9.2.17-jre7`, `9.2-jre7`, `9-jre7`, `jre7` (*9.2-jre7/Dockerfile*)](https://github.com/appropriate/docker-jetty/blob/e399f08087f8efce4a272225e667c04a09a1996b/9.2-jre7/Dockerfile)
 
 [![](https://badge.imagelayers.io/jetty:latest.svg)](https://imagelayers.io/?images=jetty:9.3.10,jetty:9.3.10-alpine,jetty:9.2.17,jetty:9.2.17-jre7)
 

lightstreamer/README.md

@@ -33,7 +33,7 @@ This will map port 8080 inside the container to port 80 on local host. Then poin
 It is possibile to customize each aspect of the Lightstreamer instance running into the container. For example, a specific configuration file may be supplied as follows:
 
 ```console
-$ docker run --name ls-server -v /path/to/my-lightstreamer-conf.xml:/lightstreamer/conf/lightstreamer_conf.xml -d -p 80:8080 lightstreamer
+$ docker run --name ls-server -v /path/to/my-lightstreamer_conf.xml:/lightstreamer/conf/lightstreamer_conf.xml -d -p 80:8080 lightstreamer
 ```
 
 In the same way, you could provide a custom logging configuration, maybe in this case also specifying a dedicated volume to ensure both the persistence of log files and better performance of the container:
@@ -55,13 +55,13 @@ FROM lightstreamer
 
 # Please specify a COPY command only for the the required custom configuration file
 COPY my-lightstreamer_conf.xml /lightstreamer/conf/lightstreamer_conf.xml
-COPY my-lightstreamer_log.xml /lightstreamer/conf/lightstreamer_log_conf.xml
+COPY my-lightstreamer_log_conf.xml /lightstreamer/conf/lightstreamer_log_conf.xml
 ```
 
 where `my-lightstreamer_conf.xml` and `my-lightstreamer_log_conf.xml` are your custom configuration files, placed in the same directory as the Dockerfile. By simply running the command:
 
 ```console
-$ docker build -t my-lightstreamer
+$ docker build -t my-lightstreamer .
 ```
 
 the new image will be built along with the provided files. After that, launch the container:
@@ -97,11 +97,11 @@ $ docker run --name ls-server -v /path/to/my-adapters:/lightstreamer/adapters -d
 In this case, the `/path/to/my-adapters` folder has to be structured with the required layout for an adapters folder:
 
 ```console
-/path/to/my-adapaters+
-                     +my_adapter_set_1
-                     +my_adapter_set_2
-                     ...
-                     +my_adapter_set_N
+/path/to/my-adapters+
+                    +my_adapter_set_1
+                    +my_adapter_set_2
+                    ...
+                    +my_adapter_set_N
                      
 ```
 

ros/README.md

@@ -60,7 +60,7 @@ The available tags include supported distros along with a hierarchy tags based o
 - `robot`: basic install for robots  
 - `perception`: basic install for perception tasks
 
-The rest of the common meta-packages such as `desktop` and `desktop-full` are hosted on automatic build repos under OSRF's Docker Hub profile [here](https://registry.hub.docker.com/u/osrf/ros). These meta-packages include graphical dependencies and hook a host of other large packages such as X11, X server, etc. So in the interest of keep the official images lean and secure, the desktop packages are just be hosted with OSRF's profile.
+The rest of the common meta-packages such as `desktop` and `desktop-full` are hosted on automatic build repos under OSRF's Docker Hub profile [here](https://hub.docker.com/r/osrf/ros/). These meta-packages include graphical dependencies and hook a host of other large packages such as X11, X server, etc. So in the interest of keep the official images lean and secure, the desktop packages are just be hosted with OSRF's profile.
 
 ### Volumes
 

sentry/README.md

@@ -130,6 +130,14 @@ It's also possible to develop custom extensions within your `onbuild` package. I
 
 See the [official Sentry documentation](https://docs.getsentry.com/on-premise/server/installation/) for more information.
 
+To create your custom `sentry:onbuild` package, simply do the following:
+
+1.	Create a Dockerfile containing `FROM sentry:onbuild`
+2.	In the same directory, add your custom configuration files.
+3.	You can get copies of those files to use as templates from the [docker-sentry GitHub repo](https://github.com/getsentry/docker-sentry/).
+4.	Build your image: `docker build -t mysentry .`
+5.	Run your custom image using `mysentry` instead of `sentry`.
+
 # License
 
 View [license information](https://github.com/getsentry/sentry/blob/master/LICENSE) for the software contained in this image.