<p>when running specific command from linux terminal command is the following:</p>
<pre><code>/opt/front/arena/sbin/ads_start  ads  -db_server vmazfassql01 -db_name Test1
</code></pre>
<p>In regular docker compose yaml file we define it like this:</p>
<pre><code>ENTRYPOINT [&quot;/opt/front/arena/sbin/ads_start&quot;, &quot;ads&quot; ]
command: [&quot;-db_server vwmazfassql01&quot;,&quot;-db_name Test1&quot;]
</code></pre>
<p>Then I tried to convert it to Kubernetes</p>
<pre><code>command: [&quot;/opt/front/arena/sbin/ads_start&quot;,&quot;ads&quot;]
args: [&quot;-db_server vwmazfassql01&quot;,&quot;-db_name Test1&quot;]
</code></pre>
<p>or without quotes for args</p>
<pre><code>command: [&quot;/opt/front/arena/sbin/ads_start&quot;,&quot;ads&quot;]
args: [-db_server vwmazfassql01,-db_name Test1]
</code></pre>
<p>but I got errors for both cases:</p>
<pre><code>Unknown parameter value '-db_server vwmazfassql01'
Unknown parameter value '-db_name Test1'
</code></pre>
<p>I then tried to remove dashes from args but then it seems those values are being ignored and not set up. During the Initialization values process, during the container start, those properties seem to have they default values e.g. db_name: &quot;ads&quot;. At least that is how it is printed out in the log during the Initialization.</p>
<p>I tried few more possibilities:
To define all of them in command:</p>
<pre><code>command:
  - /opt/front/arena/sbin/ads_start
  - ads
  - db_server vwmazfassql01
  - db_name Test1
</code></pre>
<p>To define them in little bit different way:</p>
<pre><code>command: [&quot;/opt/front/arena/sbin/ads_start&quot;,&quot;ads&quot;]
args:
  - db_server vwmazfassql01
  - db_name Test1


command: [&quot;/opt/front/arena/sbin/ads_start&quot;,&quot;ads&quot;]
args: [db_server vwmazfassql01,db_name Test1]
   
</code></pre>
<p>again they are being ignored, and not being set up.
Am I doing something wrong? How I can make some workaround for this? Thanks</p>

vel
<p>I would try separating the args, following the documentation example (<a href="https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#run-a-command-in-a-shell" rel="nofollow noreferrer">https://kubernetes.io/docs/tasks/inject-data-application/define-command-argument-container/#run-a-command-in-a-shell</a>)</p>
<p>Something like:</p>
<pre><code>command: [&quot;/opt/front/arena/sbin/ads_start&quot;, &quot;ads&quot;]
args: [&quot;-db_server&quot;, &quot;vwmazfassql01&quot;, &quot;-db_name&quot;, &quot;Test1&quot;]
</code></pre>
<p>Or maybe, it would work even like this and it looks more clean:</p>
<pre><code>command: [&quot;/opt/front/arena/sbin/ads_start&quot;]
args: [&quot;ads&quot;, &quot;-db_server&quot;, &quot;vwmazfassql01&quot;, &quot;-db_name&quot;, &quot;Test1&quot;]
</code></pre>
<p>This follows the general approach of running an external command from code (a random example is python subprocess module) where you specify each single piece of the command that means something on its own.</p>
