Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Superset-node docker compose fails to create container #9112

Closed
3 tasks
psiegrist opened this issue Feb 10, 2020 · 2 comments · Fixed by #9114
Closed
3 tasks

Superset-node docker compose fails to create container #9112

psiegrist opened this issue Feb 10, 2020 · 2 comments · Fixed by #9114

Comments

@psiegrist
Copy link

psiegrist commented Feb 10, 2020

Docker-compose off of the master branch fails to launch the superset-node container with No such file or directory

Expected results

Superset-node container starts with docker-compose.

Actual results

Superset-node container does not start with docker-compose.

The docker error is bash: line 0: cd: /app/superset-frontend: No such file or directory
Seems like this commit may have caused the problem:
2913063 (David Aaron Suddjian 2020-02-09 17:53:56 -0800 69) command: ["bash", "-c", "cd /app/superset-frontend && npm install && npm run dev"]

Screenshots

How to reproduce the bug

git clone https://github.com/apache/incubator-superset/
docker-compose up

Environment

Ubuntu 18.04.3 - AWS

Checklist

Make sure these boxes are checked before submitting your issue - thank you!

  • I have checked the superset logs for python stacktraces and included it here as text if there are any.
  • I have reproduced the issue with at least the latest released version of superset.
  • I have checked the issue tracker for the same issue and I haven't found one similar.

Additional context

Add any other context about the problem here.

@suddjian
Copy link
Member

Can you try running docker-compose build first?

@suddjian
Copy link
Member

Delving further into this, I've discovered a related issue with the Dockerfile: some files are not being copied at the correct times from the correct places. I'll have a fix up soon. docker-compose build or docker-compose up --build will still be necessary after the fix.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants