Docker Community Forums

Share and learn in the Docker community.

Panic: "no such file or directory" in Docker toolbox

(Paolougent) #1

Ok, I’m new and not sure where to head for this error. I checked this discussion, but it didn’t help much.

I’m using docker toolbox on Windows 8.1

I’m following this nice tutorial on how to make a container of a django webapp. Everything worked out almost until the end. I run the following:

docker run --publish=8001:8000 paolo/hello_django:latest

And this is what comes out:

panic: standard_init_linux.go:175: exec user process caused “no such file or directory” [recovered]
panic: standard_init_linux.go:175: exec user process caused “no such file or directory”

goroutine 1 [running, locked to thread]:
panic(0x88f8a0, 0xc820124d20)
/usr/local/go/src/runtime/panic.go:481 +0x3e6
/src/ +0x38e
panic(0x88f8a0, 0xc820124d20)
/usr/local/go/src/runtime/panic.go:443 +0x4e9*LinuxFactory).StartInitialization.
func1(0xc8200eebf8, 0xc82001a0c8, 0xc8200eed08)
/src/ +0x136*LinuxFactory).StartInitialization(
0xc820051630, 0x7fd39d996728, 0xc820124d20)
/src/ +0x5b1
main.glob.func8(0xc82006ea00, 0x0, 0x0)
/tmp/tmp.n151sEscRu/src/ +
0x68, 0x9a4d88, 0x13, 0x8ebac8, 0x4, 0xc8200ef268, 0x1, 0
x1, 0x0, 0x0, …)
/usr/local/go/src/reflect/value.go:435 +0x120d
reflect.Value.Call(0x7f45a0, 0x9a4d88, 0x13, 0xc8200ef268, 0x1, 0x1, 0x0, 0x0, 0
/usr/local/go/src/reflect/value.go:303 +0xb1, 0x9a4d88, 0xc82006ea00, 0x0, 0x0)
/src/ +0x2ee, 0x4, 0x0, 0x0, 0x0, 0x0, 0x0, 0x9842
40, 0x51, 0x0, …)
/src/ +0xfec*App).Run(0xc820001500, 0xc82000a100, 0x2, 0x2, 0x0, 0x0)
/src/ +0xaa4
/tmp/tmp.n151sEscRu/src/ +0xe2

I can add also the useless inspect:

“State”: {
“Status”: “exited”,
“Running”: false,
“Paused”: false,
“Restarting”: false,
“OOMKilled”: false,
“Dead”: false,
“Pid”: 0,
“ExitCode”: 2,
“Error”: “”,
“StartedAt”: “2016-11-16T12:36:47.537758517Z”,
“FinishedAt”: “2016-11-16T12:36:47.575430686Z”

p.s is there a way to > log.txt the output of docker run? It works with docker inspect {Container_ID} > log.txt, but not with docker run. I had to select the txt from the bash.

(Dockertiger) #2

suggest you can login the container and run the “paolo/hello_django:latest” manully .,maybe you can find why the servcie can’t start .

(Paolougent) #3

Not sure I understood what you mean. Ubuntu container seems to work. Not sure why django fail.

(Dockertiger) #4

from the result of docker inspect , you can get the details of CMD

for example “CMD [“python”, “”, “runserver”, “”]”

use the command "docker exec -it container-id /bin/bash " to login the container ,and implement the script( manully . you can check what issues happen when run the script .
but if you don’t have the skill for coding the script ,maybe it is difficult to find what happened.

(Paolougent) #5

Thanks for the patience. This does not look as anything good as CMD is null.

“Env”: [
“Cmd”: null,
“Image”: “paolo/hello_django:latest”,
“Volumes”: {
"/srv/logs/": {},
"/srv/media/": {}
“WorkingDir”: “/srv/hello_django”,
“Entrypoint”: [

I suppose you’re telling me to run Ubuntu 14.04 container and then django from there. Am I right?

I ran

docker run -it Ubuntu:14:04

as well as

docker exec -it container-id /bin/bash/

Actually it is the same to run:

docker start -i container-id

The bash starts, but now I’m confused on what should I look for.

(Dockertiger) #6

“Entrypoint”: [

this shell ,it will Launch the will find the details at the shell

(Paolougent) #7

No need to do that as I discovered it was a silly path error. I’m really a n00b.

Thanks for the header anyway.