​Having issue installing SI 6.0 Docker image
getting below error during installation at step setup the B2Bi database , here is the command
docker run -e LICENSE="accept" -e TZ=America/Detroit -d --name=ProdB2BI --net=host -v /edi/SI/downloads/prereqs:/ibm/resources 1bcb26930832 b2bi_setup deploy_db

Error message from the log...

': not a valid identifieriDockerStart.sh: line 65: export: `
Please provide a valid number of seconds for soft stop timeout in the configurat                                      ion file

------------------------------
MOHAMMED HAJI
------------------------------

#SupplyChain
#B2BIntegration

Hi Mohammed,

Check your setup.cfg (see https://www.ibm.com/support/knowledgecenter/en/SS3JSW_6.0.0/installing/installing/integrator/SI_Creating_setupcfg.html).

What value do you have assigned to SOFT_STOP_TIMEOUT= ? It is optional so you can leave it out completely but if it's in there (like in the sample in the docs) you have to assign a value (number of seconds - recommendation is a minimum of 10).

------------------------------
RICHARD CROSS
------------------------------

------Original Message------

Hi Mohammed,

Check your setup.cfg (see https://www.ibm.com/support/knowledgecenter/en/SS3JSW_6.0.0/installing/installing/integrator/SI_Creating_setupcfg.html).

What value do you have assigned to SOFT_STOP_TIMEOUT= ? It is optional so you can leave it out completely but if it's in there (like in the sample in the docs) you have to assign a value (number of seconds - recommendation is a minimum of 10).

------------------------------
RICHARD CROSS
------------------------------

#SupplyChain
#B2BIntegration

Hi Mohammed,

Looks like a issue with setup.cfg file, could you please share the setup.cfg you created.

Here is the product link for sample setup.cfg

Regards,
Girish

------------------------------
Girish Venkatesh
------------------------------

Hi Mohammed,

I ran into a similar issue when doing a docker installation a few months back.  If your setup.cfg file was created/modified/saved on a Windows machine then check if there are any Windows newline characters in the file; the installation process will fail if Windows newline characters exist.  Support had recommended the following to me:

"I would suggest recreating the setup.cfg file under your Linux system directly. See what happens once you run that command again. Or you could just replace all \r\n newline characters with \n"


Would suggest looking through your setup.cfg file, replace any Windows newline characters and see if that allows the command to complete.

------------------------------
Chris Techter
Principal Architect - CoEnterprise
------------------------------