From 481b84ba9dae9c9fb34f98eca2c0b687258de95c Mon Sep 17 00:00:00 2001
From: Arthur De Magalhaes <arthurdm@ca.ibm.com>
Date: Mon, 27 Apr 2020 16:49:51 -0400
Subject: [PATCH] Update content.md

---
 websphere-liberty/content.md | 4 +++-
 1 file changed, 3 insertions(+), 1 deletion(-)

diff --git a/websphere-liberty/content.md b/websphere-liberty/content.md
index 53e445b93..4438480de 100644
--- a/websphere-liberty/content.md
+++ b/websphere-liberty/content.md
@@ -132,13 +132,15 @@ To elaborate these capabilities this section assumes the standalone Spring Boot
 	FROM %%IMAGE%%:kernel as staging
 	COPY --chown=1001:0 hellospringboot.jar /staging/myFatApp.jar
 	COPY --chown=1001:0 server.xml /config/
-	RUN configure.sh && springBootUtility thin \
+	RUN springBootUtility thin \
 	   --sourceAppPath=/staging/myFatApp.jar \
 	   --targetThinAppPath=/staging/myThinApp.jar \
 	   --targetLibCachePath=/staging/lib.index.cache
 	FROM %%IMAGE%%:kernel
+	COPY --chown=1001:0 server.xml /config
 	COPY --from=staging /staging/lib.index.cache /lib.index.cache
 	COPY --from=staging /staging/myThinApp.jar /config/dropins/spring/myThinApp.jar
+	RUN configure.sh
 	```
 
 	For Spring Boot applications packaged with library dependencies that rarely change across continuous application updates, you can use the capabilities mentioned above to to share library caches across containers and to create even more efficient docker layers that leverage the docker build cache.