mistercrunch commented on issue #10149: URL: https://github.com/apache/superset/issues/10149#issuecomment-2524736725
the "Start the latest official release of Superset" instructions point to the `docker-compose-image-tag.yml` which should point to the latest release, currently `4.1.1`. Let me double check and leave a trace here: - if no `TAG` env var is specified, we point to `latest-dev` image tag on docker hub [relevant line](https://github.com/apache/superset/blob/master/docker-compose-image-tag.yml#L24) - this is [the latest-dev](https://hub.docker.com/layers/apache/superset/latest-dev/images/sha256-d2aa511163d0c3ff21ddd33ab85a089625c36a1f4c3fe12b279a3459c98a40e2?context=explore) image on docker-hub, pushed 18 days ago which looks about right, lines up with the 4.1.1 release from 2 weeks ago - all docker-compose are supposed to execute [this script](https://github.com/apache/superset/blob/master/docker/docker-init.sh#L59-L64), which should create the `admin` user, you shouldn't have to do the incantations specified in comments above, at least not if you're using `docker-compose` - tested `docker-compose -f docker-compose-image-tag.yml up` locally, seems to work just fine If you have history of running different versions and/or doing development you may want to try nuking the postgres db to start from a clean slate: https://superset.apache.org/docs/contributing/development/#nuking-the-postgres-database There's also other potential issue if you're not vanilla and for instance have setup your own `pythonpath`/config file or if you have ENV VARs defined that can affect the docker-compose behavior, for instance you'll see people that have set up env vars to point the database to a local instance over the docker-provided one in their `.bash_profile` and that throws off the setup. -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
