-2

I am trying to run Apache Superset locally. I am following these instructions. When I write the command "docker compose up", all the containers seem to be running okay, but when I check the browser on localhost 8088, I just get a loading page:.

With the command docker-compose -f docker-compose-non-dev.yml up, the page loads.

What I want to do at the end of the day is to modify superset's frontend.

f_puras
  • 2,521
  • 4
  • 33
  • 38
Angel Ortiz
  • 72
  • 13
  • If you want to modify the frontend code, you should run backend and frontend separately as stated in this instruction: https://github.com/apache/superset/blob/master/CONTRIBUTING.md#flask-server – artemonsh Jan 23 '23 at 09:21

2 Answers2

0

I had a similar issue, restarting the docker service fixed it. Are you running the default SQLITE database or a local instance of a database?

Lenin
  • 303
  • 2
  • 3
  • 1
    I am literally forking, cloning the repo. Then I run `docker-compose-up` and nothing more. It stays there forever. The docker compose non dev seems to load but I still can't see any changes – Angel Ortiz Jan 20 '23 at 15:19
0

I had a similar issue, and pulled a different version (2.0.0-dev) of the image instead of the default latest as the latest docker image has lots of bugs:

Modify the docker compose file with "x-superset-image: &superset-image apache/superset:2.0.0-dev",

Use Postgre v10 on the db section. db: env_file: docker/.env-non-dev image: postgres:10

PeteBright
  • 1