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/02/20 18:05:24 UTC

[GitHub] iaperez commented on issue #6887: docker-compose up fails with "superset_superset_1 exited with code 243"

iaperez commented on issue #6887: docker-compose up fails with "superset_superset_1 exited with code 243"
URL: https://github.com/apache/incubator-superset/issues/6887#issuecomment-465690374
 
 
   try upgrading docker-compose to the last version... at least 1.23.2
   
   I had the same issue, and after some investigation, I got that the owner of the superset/assets folder was not superset. I was planning to add "RUN chmod -R ..." after the docker copy command on the Dockerfile. But then I decided to check the versions of docker and docker compose.
   I upgraded docker compose,   and now is working for me.
   
   

----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on 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