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

[inamilu]

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!

[inamilu]

The problem was with the Windows line endings. After changing the .ssh files to Unix line endings, the container is up and running.

[ctivanovich]

Hi I'm having this same error, only, it's for attempting to build the container on Windows, and I haven't gotten past the docker-compose run --rm superset ./docker-init.sh step. I've looked through the log, which states:
standard_init_linux.go:207: exec user process caused "no such file or directory". The container is attempting to run, I think, /entrypoint.sh, but that I think exists within the container's system, not in the filesystem of incubator-superset, so I can't access it. The postgres and redis containers seem to be running fine. Do you have any idea on how I might solve this problem? I had hoped that using superset in this container would help me get around the Windows compatibility issues.

[csakaszamok]

Same error for me

[ctivanovich]

I also tried dos2unix to change the line endings using WSL, but that didn't help, the error remains the same.

[kumaranar]

Same error for me

[Mattmtech]

@inamilu which ssh files did you change the file type on? do you mean the .sh files?

[chharish]

same issue here. the health check never starts and the container keep restarting again and again.

[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

[ramonankersmit]

This solves the original error but after entering password etc you get this error:
NotADirectoryError: [Errno 20] Not a directory: '/home/superset/superset/static/assets/package.json'