Using the rancher container exec api

[3goats]

Hi,

I'm trying to get this to work via the rancher container exec api. It works fine from the command line

sudo docker exec -i 3e8756acf56815459b7a50e36f889b1126792caf1fa14c6b7103678cfaf5d009 sh -c 'echo hello 123 >/data.txt

However if I make this request via the Rancher REST API:

HTTP/1.1 POST /v2-beta/projects/1a5/containers/1i177/?action=execute
Host: 192.168.13.129:8080
Accept: application/json
Content-Type: application/json
Content-Length: 98

{
"attachStdin": true,
"attachStdout": true,
"command": [
"sh -c 'echo hello 456 >/data.txt"
],
"tty": true
}

It returns the following error.

rpc error: code = 2 desc = oci runtime error: exec failed: exec: "sh -c 'echo hello 456 >/data.txt": stat sh -c 'echo hello 456 >/data.txt: no such file or directory

[3goats]

I've also broken down my commands as follows:

{
	"attachStdin": true,
	"attachStdout": true,
	"command": [
         "sh",
         "-c",
         "/'touch /test.txt/'"

],
	"tty": true
}

However, I'm still unable to make this work.

Carl

[akurkin]

Have you tried using /v1/ API?

[3goats]

No - I'll give that a try. Thanks, Carl

…

Sent from my iPhone

On 22 Dec 2016, at 16:48, Alex Kurkin ***@***.***> wrote: Have you tried using /v1/ API? — You are receiving this because you authored the thread. Reply to this email directly, view it on GitHub, or mute the thread.

[3goats]

Just tried the V1 API. Seems to be the same behaviour.

[3goats]

Hi - are there any details docs or working examples here? All of my examples work using the Docker command line exec. However, I cannot get anything other than a basic "ls" to work using the Rancher API.