lint errors fix

Author: adhrames

OracleSOASuite/dockerfiles/14.1.2.0/Containerfile

@@ -36,19 +36,19 @@ COPY patches/* /u01/patches/
 COPY opatch_patch/* ${OPATCH_PATCH_DIR}/
 COPY container-scripts/* /u01/oracle/container-scripts/
 
-#WORKDIR /u01
-RUN  cd /u01 && chmod 755 ./*.jar && \
+WORKDIR /u01
+RUN  chmod 755 ./*.jar && \
      chmod +xr /u01/oracle/container-scripts/*.*
 
-#WORKDIR /u01/oracle
+WORKDIR /u01/oracle
 #
 # Copy files and packages for install
 # -----------------------------------
 USER oracle
 COPY install/* /u01/
 
-#WORKDIR /u01
-RUN cd /u01 && "$JAVA_HOME/bin/java" -jar "$FMW_JAR1" -silent -responseFile /u01/soasuite.response -invPtrLoc /u01/oraInst.loc -jreLoc "$JAVA_HOME" -ignoreSysPrereqs -force -novalidation ORACLE_HOME="$ORACLE_HOME" && \
+WORKDIR /u01
+RUN "$JAVA_HOME/bin/java" -jar "$FMW_JAR1" -silent -responseFile /u01/soasuite.response -invPtrLoc /u01/oraInst.loc -jreLoc "$JAVA_HOME" -ignoreSysPrereqs -force -novalidation ORACLE_HOME="$ORACLE_HOME" && \
   "$JAVA_HOME/bin/java" -jar "$FMW_JAR2" -silent -responseFile /u01/osb.response -invPtrLoc /u01/oraInst.loc -jreLoc "$JAVA_HOME" -ignoreSysPrereqs -force -novalidation ORACLE_HOME="$ORACLE_HOME" INSTALL_TYPE="Service Bus" && \
   "$JAVA_HOME/bin/java" -jar "$FMW_JAR3" -silent -responseFile /u01/b2b.response -invPtrLoc /u01/oraInst.loc -jreLoc "$JAVA_HOME" -ignoreSysPrereqs -force -novalidation ORACLE_HOME="$ORACLE_HOME" INSTALL_TYPE="B2B" && \
   rm -fr /u01/*.jar /u01/*.response
@@ -58,10 +58,11 @@ RUN cd /u01 && "$JAVA_HOME/bin/java" -jar "$FMW_JAR1" -silent -responseFile /u01
 # ------------------
 #
 
-#WORKDIR ${OPATCH_PATCH_DIR}
+WORKDIR ${OPATCH_PATCH_DIR}
 RUN opatchzip=`ls ${OPATCH_PATCH_DIR}/p*.zip 2>/dev/null`; \
     if [ ! -z "$opatchzip" ]; then \
-      cd ${OPATCH_PATCH_DIR} && echo -e "\nApplying the below OPatch patch present in ${OPATCH_PATCH_DIR} directory."; \
+#      cd ${OPATCH_PATCH_DIR};  \
+      echo -e "\nApplying the below OPatch patch present in ${OPATCH_PATCH_DIR} directory."; \
       ls p*.zip; \
       echo -e ""; \
       echo "Extracting patch: ${opatchzip}"; \
@@ -79,10 +80,11 @@ RUN opatchzip=`ls ${OPATCH_PATCH_DIR}/p*.zip 2>/dev/null`; \
 # Apply SOA Patches
 # -----------------
 
-#WORKDIR /u01/patches
+WORKDIR /u01/patches
 RUN export OPATCH_NO_FUSER=TRUE && patchzips=`ls /u01/patches/p*.zip 2>/dev/null`; \
     if [ ! -z "$patchzips" ]; then \
-      cd /u01/patches && echo -e "\nBelow patches present in patches directory. Applying these patches:"; \
+#      cd /u01/patches;  \
+      echo -e "\nBelow patches present in patches directory. Applying these patches:"; \
       ls p*.zip; \
       echo -e ""; \
       for filename in `ls p*.zip`; do echo "Extracting patch: ${filename}"; $JAVA_HOME/bin/jar xf ${filename}; done; \
@@ -91,7 +93,8 @@ RUN export OPATCH_NO_FUSER=TRUE && patchzips=`ls /u01/patches/p*.zip 2>/dev/null
       $ORACLE_HOME/OPatch/opatch util cleanup -silent; \
       rm -rf /u01/patches /u01/oracle/cfgtoollogs/opatch/*; \
       echo -e "\nPatches applied in SOA oracle home are:"; \
-      cd $ORACLE_HOME/OPatch && $ORACLE_HOME/OPatch/opatch lspatches; \
+      cd $ORACLE_HOME/OPatch; \
+      $ORACLE_HOME/OPatch/opatch lspatches; \
     else \
       echo -e "\nNo patches present in patches directory. Skipping patch application."; \
     fi && \
@@ -107,7 +110,7 @@ RUN export OPATCH_NO_FUSER=TRUE && patchzips=`ls /u01/patches/p*.zip 2>/dev/null
         gzip /u01/oracle/cfgtoollogs/opatch/*.log; \
     fi
 
-#WORKDIR /u01/oracle
+WORKDIR /u01/oracle
 #
 # Rebuild from base image
 # -----------------------

OracleSOASuite/dockerfiles/14.1.2.0/README.md

@@ -23,7 +23,6 @@ To create the Podman network and run containers, follow these steps:
 
 ## 1. Create a network
 
-
 The containers will be connected using a Podman user-defined network.
 
 ### Create a user-defined network
@@ -38,7 +37,7 @@ For example:
 
 ## 2. Mount a host directory as a data volume
 
-Data volumes are designed to persist data, independent of the container’s lifecycle. Podman automatically creates volumes when you specify a volume name with the -v option, without the need to predefine directories on the host. In this project, the volumes will be used to store Database data files and WebLogic Server domain files. These volumes will be automatically created and managed by Podman. The names of the volumes are specified in the podman run commands. 
+Data volumes are designed to persist data, independent of the container’s lifecycle. Podman automatically creates volumes when you specify a volume name with the -v option, without the need to predefine directories on the host. In this project, the volumes will be used to store Database data files and WebLogic Server domain files. These volumes will be automatically created and managed by Podman. The names of the volumes are specified in the podman run commands.
 
 `$ podman -d --name soadb -v soadb_vol:/opt/oracle/oradata`
 
@@ -69,18 +68,18 @@ The Oracle database server container requires custom configuration parameters fo
 
 To run the database container to host the RCU schemas:
 
-1.  Add the following parameters to a `db.env.txt` file:
+1. Add the following parameters to a `db.env.txt` file:
     ``` bash
     ORACLE_SID=soadb
     ORACLE_PDB=soapdb
     ORACLE_PWD=Oradoc_db1
     ENABLE_ARCHIVELOG=true
     ```
-1.  Enter the following command:
+1. Enter the following command:
     ``` bash
     `$ podman run -d --name soadb --network=SOANet -p 1521:1521 -p 5500:5500 -v soadb_vol:/opt/oracle/oradata --env-file ./db.env.txt container-registry.oracle.com/database/enterprise:19.3.0.0`
     ```
-1.  Verify that the database is running and healthy. The `STATUS` field should show `healthy` in the output of `podman ps`.
+1. Verify that the database is running and healthy. The `STATUS` field should show `healthy` in the output of `podman ps`.
 
 ## 4. Obtain the SOA 14.1.2.0 container image
 
@@ -104,7 +103,7 @@ ADMIN_PORT=<Node port number mapping Administration Server container port `7001`
 PERSISTENCE_STORE=<jdbc | file>
 ```
 >IMPORTANT: `DOMAIN_TYPE` must be carefully chosen and specified depending on the use case. It can't be changed once you proceed.
-For Oracle SOA Suite domains, the supported domain types are `soa`, `osb` and `soaosb`. 
+For Oracle SOA Suite domains, the supported domain types are `soa`, `osb` and `soaosb`.
 - soa       : Deploys a SOA Domain with Enterprise Scheduler (ESS)
 - osb       : Deploys an OSB Domain (Oracle Service Bus)
 - soaosb    : Deploys a Domain with SOA, OSB and Enterprise Scheduler (ESS)
@@ -133,7 +132,7 @@ For example:
 ```
 The options `-it` in the above command runs the container in interactive mode and you will be able to see the commands running in the container. This includes the command for RCU creation, domain creation, and configuration, followed by starting the Administration Server.
 
-> IMPORTANT: You need to wait until all the above commands are run before you can access the Administration Server Web Console. The following lines highlight when the Administration Server is ready to be used:    
+> IMPORTANT: You need to wait until all the above commands are run before you can access the Administration Server Web Console. The following lines highlight when the Administration Server is ready to be used:
 ``` bash
 INFO: Admin server is running
 
@@ -269,7 +268,7 @@ For example:
 ``` bash
 `$ podman run -it --name osbms1 --network=SOANet -p 8004:8004 -v soadomain_vol:/u01/oracle/user_projects --env-file ./osbserver2.env.list container-registry.oracle.com/middleware/soasuite:14.1.2.0-17-ol8-241205 "/u01/oracle/container-scripts/startMS.sh"`
 ```
-The following lines indicate when the Oracle Service Bus Managed Server is ready to be used: 
+The following lines indicate when the Oracle Service Bus Managed Server is ready to be used:
 ``` bash   
 INFO: Managed Server is running