apimastery commented on issue #6291: Cannot connect to amqp://guest:**@127.0.0.1:5672 URL: https://github.com/apache/incubator-superset/issues/6291#issuecomment-437220076 There are other open issues for the same problem, it seems: - https://github.com/apache/incubator-superset/issues/5987 - https://github.com/apache/incubator-superset/issues/5919 Here is what worked for me: In `docker-compose.yml`, comment out the volumes config - the Docker image already contains those directories and their files: ``` #volumes: # - .:/home/work/incubator-superset # - superset-node-modules:/home/work/incubator-superset/superset/assets/node_modules ``` Then execute: `docker-compose up -d` `docker-compose exec superset bash` Once inside the container, edit `docker-init.sh` (e.g. using `vim` or `vi`) - comment out the `npm run build` command: `# cd superset/assets && npm run build && cd ../../` The command isn't really needed because the Docker image build runs it. Next start the application up by executing: `bash docker-init.sh` I'm glad to see recent commits to the master branch to fix in in `docker-init.sh` the host (0.0.0.0) so the container is accessible from something other than localhost and port (8088) to match the port in docker-compose.yml so the health check succeeds... HTH
---------------------------------------------------------------- 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: [email protected] With regards, Apache Git Services --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
