Incubator-superset container fails: exec user process caused "no such file or directory"

Hello everyone,

I’m trying to install Superset with the help of Docker, but after running the following command: docker-compose up -d the status of the apache/incubator-superset container remains in Restarting, i.e. it keeps restarting again and again. Clearly some error is causing the container to fail, so the restart policy is restarting it repeatedly. As a consequence, I can’t run the next command: docker-compose exec superset bash since, the following error is thrown: Error response from daemon: Container fa5138... is restarting, wait until the container is running

Does anyone has any idea where the problem could be?

EDIT: After running docker logs to see the outputs the container is generating, I got the following error message: 2018-11-02T10:46:06.217791002Z standard_init_linux.go:190: exec user process caused "no such file or directory"

Thank you in advance!

[csakaszamok]

Same error for me

[gaorongchao]

I try one possible solution. when your user docker in windows:

• git config --global core.autocrlf input this made the file end with LF when your git clone in windows.

docker-compose run --rm superset ./docker-init.sh docker-compose up

---

if there still have some problem,please continue

• bulid superset by hand, docker build -f ./contrib/docker/Dockerfile -t="supset-1" . this is run in root. and You will get the build image, such like c25ef5300307
• modify ./contrib/docker/docker-compose.yml

  superset:
    image: c25ef5300307
    # build:
    #   context: ../../
    #   dockerfile: contrib/docker/Dockerfile
    restart: unless-stopped
    environment:
......

• finally: cd /contrib/docker docker-compose run --rm superset ./docker-init.sh docker-compose up