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 17:34:35 UTC

[GitHub] gchehab edited a comment on issue #6887: docker-compose up fails with "superset_superset_1 exited with code 243"

gchehab edited a comment 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-465678766
 
 
   The problem occurs only in development mode because the docker-compose.yml file maps a volume /home/superset/superset using the ../../superset path (relative to the contrib/docker). 
   
   ```
   (...)
   version: '3'
   services:
     (...)
     superset:
     (...)
     volumes:
       (...)
       # this is needed to communicate with the postgres and redis services
       - ./superset_config.py:/home/superset/superset/superset_config.py
       # this is needed for development, remove with SUPERSET_ENV=production
       - ../../superset:/home/superset/superset
   ```
   
   When it gets up, on the container, the volume is mounted with root ownership (or whatever user starts docker-composer), and superset tries to run with its own user `superset`.
   
   An ugly workaround is to add `user: root:root` directive to the superset section of services. It states that the user who will run the `entrypoint.sh` is root -- or the owner of the `../../superset` path. 
   
   ```
   (...)
   version: '3'
   services:
     (...)
     superset:
     (...)
     user: root:root
     volumes:
       (...)
       # this is needed to communicate with the postgres and redis services
       - ./superset_config.py:/home/superset/superset/superset_config.py
       # this is needed for development, remove with SUPERSET_ENV=production
       - ../../superset:/home/superset/superset
   ```

----------------------------------------------------------------
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