#!/bin/bash -i when to use it in a docker file

I need to understand when I need to use the -i .

It’s a convention so the *nix shell knows what kind of interpreter to run.

For example, older flavors of ATT defaulted to sh (the Bourne shell), while older versions of BSD defaulted to csh (the C shell).

Even today (where most systems run bash, the “Bourne Again Shell”), scripts can be in bash, python, perl, ruby, PHP, etc, etc. For example, you might see #!/bin/perl or #!/bin/perl5.

Not able to git pull “/bin/bash: /usr/bin/sss_ssh_knownhostsproxy: No such file or directory”

I am not able to pull from jenkins slave machine, getting below error:

$ git pull

“/bin/bash: /usr/bin/sss_ssh_knownhostsproxy: No such file or directory ssh_exchange_identification: Connection closed by remote host fatal: Could not read from remote repository.

Please make sure you have the correct access rights and the repository exists.”

deployment key already added in the remote repo.

Below are the output of git host:

$ ssh -vvv git@github.com

” OpenSSH_7.6p1 Ubuntu-4ubuntu0.3, OpenSSL 1.0.2n 7 Dec 2017

debug1: Reading configuration data /etc/ssh/ssh_config

debug1: /etc/ssh/ssh_config line 23: Applying options for *

debug1: Executing proxy command: exec /usr/bin/sss_ssh_knownhostsproxy -p 22 github.com

debug1: permanently_drop_suid: 1001

debug1: identity file /home/jenkins/.ssh/id_rsa type 0

debug1: key_load_public: No such file or directory

debug1: identity file /home/jenkins/.ssh/id_rsa-cert type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/jenkins/.ssh/id_dsa type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/jenkins/.ssh/id_dsa-cert type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/jenkins/.ssh/id_ecdsa type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/jenkins/.ssh/id_ecdsa-cert type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/jenkins/.ssh/id_ed25519 type -1

debug1: key_load_public: No such file or directory

debug1: identity file /home/jenkins/.ssh/id_ed25519-cert type -1

debug1: Local version string SSH-2.0-OpenSSH_7.6p1 Ubuntu-4ubuntu0.3

/bin/bash: /usr/bin/sss_ssh_knownhostsproxy: No such file or directory

ssh_exchange_identification: Connection closed by remote host”

i am facing this issue recently, earlier it was working smoothly. i didn’t make any changes. interesting thing is if i create salve from old AMI then git pull if working but after adding new machine as new jenkins slave it stops working.