Bash Script fails with error: OCI runtime exec failed

Question

I am running the below script and getting error.

#!/bin/bash
webproxy=$(sudo docker ps -a --format "{{.Names}}"|grep webproxy)
webproxycheck="curl -k -s https://localhost:\${nginx_https_port}/HealthCheckService"
if [ -n "$webproxy" ] ; then
  sudo docker exec $webproxy sh -c "$webproxycheck"
fi

Here is my docker ps -a output

$sudo docker ps -a --format "{{.Names}}"|grep webproxy
webproxy-dev-01
webproxy-dev2-01

when i run the command individually it works. For Example:

$sudo docker exec webproxy-dev-01 sh -c 'curl -k -s https://localhost:${nginx_https_port}/HealthCheckService'
HEALTHCHECK_OK

$sudo docker exec webproxy-dev2-01 sh -c 'curl -k -s https://localhost:${nginx_https_port}/HealthCheckService'
HEALTHCHECK_OK

Here is the error i get.

$ sh healthcheck.sh
OCI runtime exec failed: exec failed: container_linux.go:348: starting container process caused "exec: \"webproxy-dev-01\": executable file not found in $PATH": unknown

Could someone please help me with the error. Any help will be greatly appreciated.

You don't need sudo or docker exec for this at all; you should be able to just invoke that curl command against a published port for your container. — David Maze
– David Maze, Commented Aug 29, 2020 at 17:46
sudo docker is necessary on some platforms like Red Hat, but e.g. on Debian-based platforms you should simply add your user to the docker group and then run docker without sudo. — tripleee
– tripleee, Commented Oct 10, 2020 at 9:06

tripleee · Accepted Answer · 2020-10-10 09:04:45Z

1

Because the variable contains two tokens (on two separate lines) that's what the variable expands to. You are running

sudo docker exec webproxy-dev-01 webproxy-dev2-01 ...

which of course is an error.

It's not clear what you actually expect to happen, but if you want to loop over those values, that's

for host in $webproxy; do
    sudo docker exec "$host" sh -c "$webproxycheck"
done

which will conveniently loop zero times if the variable is empty.

If you just want one value, maybe add head -n 1 to the pipe, or pass a more specific regular expression to grep so it only matches one container. (If you have control over these containers, probably run them with --name so you can unambiguously identify them.)

edited Oct 10, 2020 at 9:04

answered Aug 29, 2020 at 14:15

tripleee

192k37 gold badges318 silver badges367 bronze badges

Sign up to request clarification or add additional context in comments.

Comments

Sara James · Accepted Answer · 2020-09-01 20:18:20Z

0

Based on your given script, you are trying to "exec" the following

sudo docker exec webproxy-dev2-01
webproxy-dev-01 sh -c "curl -k -s https://localhost:${nginx_https_port}/HealthCheckService"

As you see, here is your error.

sudo docker exec webproxy-dev2-01
webproxy-dev-01 [...]

The problem is this line:

webproxy=$(sudo docker ps -a --format "{{.Names}}"|grep webproxy)

which results in the following (you also posted this):

webproxy-dev2-01 
webproxy-dev-01

Now, the issue is, that your docker exec command now takes both images names (coming from the variable assignment $webproxy), interpreting the second entry (which is webproxy-dev-01 and sepetrated by \n) as the exec command. This is now intperreted as the given command which is not valid and cannot been found: That's what the error tells you.

A workaround would be the following:

webproxy=$(sudo docker ps -a --format "{{.Names}}"| grep webproxy | head -n 1)

It only graps the first entry of your output. You can of course adapt this to do this in a loop.

A small snippet:

#!/bin/bash

webproxy=$(sudo docker ps -a --format "{{.Names}}"| grep webproxy )
echo ${webproxy}

webproxycheck="curl -k -s https://localhost:\${nginx_https_port}/HealthCheckService"

while IFS= read -r line; do
    if [ -n "$line" ] ; then
        echo "sudo docker exec ${line} sh -c \"${webproxycheck}\""
    fi   
done <<< "$webproxy"

edited Sep 1, 2020 at 20:18

Sara James

1333 silver badges15 bronze badges

answered Aug 29, 2020 at 13:50

agentsmith

1,3242 gold badges15 silver badges39 bronze badges

1 Comment

tripleee Over a year ago

In the OP's original code, the variable is not quoted, so the newline between the values is normalized to a single space by the shell.

Collectives™ on Stack Overflow

Bash Script fails with error: OCI runtime exec failed

2 Answers 2

Comments

1 Comment

Your Answer

Linked

Hot Network Questions

Collectives™ on Stack Overflow

2 Answers 2

Comments

1 Comment

Your Answer

Sign up or log in

Post as a guest

Linked

Related