You are viewing a plain text version of this content. The canonical link for it is here.
Posted to notifications@superset.apache.org by GitBox <gi...@apache.org> on 2019/04/01 10:51:28 UTC

[GitHub] [incubator-superset] ctivanovich edited a comment on issue #6267: Incubator-superset container fails: exec user process caused "no such file or directory"

ctivanovich edited a comment on issue #6267: Incubator-superset container fails: exec user process caused "no such file or directory"
URL: https://github.com/apache/incubator-superset/issues/6267#issuecomment-478530762
 
 
   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 as a container would help me get around the Windows compatibility issues.

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
 
For queries about this service, please contact Infrastructure at:
users@infra.apache.org


With regards,
Apache Git Services

---------------------------------------------------------------------
To unsubscribe, e-mail: notifications-unsubscribe@superset.apache.org
For additional commands, e-mail: notifications-help@superset.apache.org