<p>In my use case I would like to have two jar files in the containers. In typical docker image, I see an entry point, which basically starts the jar file. In my case, I will not know which program to be started, till the time the container is getting used in the K8s services. In my example, I have a jar file that applies the DDLs and the second Jar file is my application. I want the k8s to deploy my DDL application first and upon completion it will deploy my spring boot application (from a different jar but from same container ) next. There by I cannot give an entry point for my container, rather I need to run the specific jar file using command and argument from my yaml file. In all the examples I have come across, I see an entry point being used to start my java process. </p>

<p>The difference here from the post referred here is- i want to have the container to have two jar files and when I load the container through k8s, I want to decide which program to run from command prompt. One option I am exploring is to have a parametrized shell script, so I can pass the jar name as parameter and the shell will run java -jar . I will update here once I find something</p>

<p><strong>solution update</strong>
Add two jars in the docker file and have a shell script that uses parameter. Use the below sample to invoke the right jar file form the K8s yaml file</p>

<p>spec:  containers:<br>
- image: URL
  imagePullPolicy: Always  name: image-name
  command: ["/bin/sh"] 
  args: ["-c", "/home/md/javaCommand.sh jarName.jar"]<br>
  ports:  - containerPort: 8080<br>
  name: http</p>

vinSan
<p>A docker image doesn't have to run a java jar when starting, it has to run something.</p>

<p>You can simply make this something a bash script that will make these decisions and start the jar you like</p>
