mjhjmtu

I have an expect script, and want to spawn a BASH command for it to provide input to. When I use the following syntax:

spawn /bin/bash docker run -v $OVPN_DATA:/etc/openvpn --rm -it kylemanna/openvpn ovpn_initpki`

or:

spawn docker run -v $OVPN_DATA:/etc/openvpn --rm -it kylemanna/openvpn ovpn_initpki

I get the following error:

bad flag "-it": must be -glob, -regexp, -exact, -notransfer, -nocase, -i, -
indices, -iread, -timestamp, -timeout, -nobrace, or --
 while executing
"expect {
 spawn (/bin/bash) docker run -v $OVPN_DATA:/etc/openvpn --rm -it kylemanna/openvpn 
ovpn_initpki
 "Enter PEM pass phrase:" {send "DefPEMVPNPassPhra..."
 (file "addcontainer.exp" line 7)

How do I tell expect to spawn a BASH command?

The output suggests that spawn doesn't stop interpreting flags when it encounters a command name.

A common convention is to use -- as a separator between options for a command (which it should parse and interpret), and arguments to things it needs to call (which it should ignore and pass on).

The spawn output lists -- as one of the possible options, which suggests that it follows that convention. Try specifying it?

spawn /bin/bash -- -c "docker run ..."

try:

spawn /bin/bash
send "docker run -v $OVPN_DATA:/etc/openvpn --rm -it kylemanna/openvpn ovpn_initpki"