Skip to main content
grammar tweaks
Source Link
Jeff Schaller
  • 68.8k
  • 35
  • 122
  • 265

Just a guess:

You aare trying to run a Bash built-in command in a chroot like this:

chroot <PATH> bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>

But your chroot doesn't have any interpreter running, which could understand bind. Does the following work:

chroot <PATH> bash -c "bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>"

PS
As @mosvy said, first as answer and then as comment, you can pass the enviromentenvironment with the call of chroot:

INPUTRC=/path/to/inputrc chroot <jail> bash 

Just a guess:

You a trying to run a Bash built-in command in a chroot like this:

chroot <PATH> bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>

But your chroot doesn't have any interpreter running, which could understand bind. Does the following work:

chroot <PATH> bash -c "bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>"

PS
As @mosvy said, first as answer and then as comment, you can pass the enviroment with the call of chroot:

INPUTRC=/path/to/inputrc chroot <jail> bash 

Just a guess:

You are trying to run a Bash built-in command in a chroot like this:

chroot <PATH> bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>

But your chroot doesn't have any interpreter running, which could understand bind. Does the following work:

chroot <PATH> bash -c "bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>"

PS
As @mosvy said, first as answer and then as comment, you can pass the environment with the call of chroot:

INPUTRC=/path/to/inputrc chroot <jail> bash 
added 3 characters in body
Source Link
WGRM
  • 828
  • 4
  • 15

Just a guess:

You a trying to run a Bash built-in command in a chroot like this:

chroot <PATH> bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>

But your chroot doesn't have any interpreter running, which could understand bind. Does the following work:

chroot <PATH> bash -c "bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>"

PS 
As mosvy@mosvy said, first as answer and then as comment, you can pass the enviroment with the call of chroot:

INPUTRC=/path/to/inputrc chroot <jail> bash 

Just a guess:

You a trying to run a Bash built-in command in a chroot like this:

chroot <PATH> bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>

But your chroot doesn't have any interpreter running, which could understand bind. Does the following work:

chroot <PATH> bash -c "bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>"

PS As mosvy said, first as answer and then as comment, you can pass the enviroment with the call of chroot:

INPUTRC=/path/to/inputrc chroot <jail> bash 

Just a guess:

You a trying to run a Bash built-in command in a chroot like this:

chroot <PATH> bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>

But your chroot doesn't have any interpreter running, which could understand bind. Does the following work:

chroot <PATH> bash -c "bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>"

PS 
As @mosvy said, first as answer and then as comment, you can pass the enviroment with the call of chroot:

INPUTRC=/path/to/inputrc chroot <jail> bash 
added 164 characters in body
Source Link
WGRM
  • 828
  • 4
  • 15

Just a guess:

You a trying to run a Bash built-in command in a chroot like this:

chroot <PATH> bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>

But your chroot doesn't have any interpreter running, which could understand bind. Does the following work:

chroot <PATH> bash -c "bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>"

PS As mosvy said, first as answer and then as comment, you can pass the enviroment with the call of chroot:

INPUTRC=/path/to/inputrc chroot <jail> bash 

Just a guess:

You a trying to run a Bash built-in command in a chroot like this:

chroot <PATH> bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>

But your chroot doesn't have any interpreter running, which could understand bind. Does the following work:

chroot <PATH> bash -c "bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>"

Just a guess:

You a trying to run a Bash built-in command in a chroot like this:

chroot <PATH> bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>

But your chroot doesn't have any interpreter running, which could understand bind. Does the following work:

chroot <PATH> bash -c "bind -f <PATH_IN_CHROOT>/.inputrc && <PROGRAM_TO_RUN>"

PS As mosvy said, first as answer and then as comment, you can pass the enviroment with the call of chroot:

INPUTRC=/path/to/inputrc chroot <jail> bash 
Source Link
WGRM
  • 828
  • 4
  • 15
Loading