Bug description

I'm currently setting up Apache Superset using the docker-compose-image-tag.yml file, and getting below error

Image

my .env file in the docker folder is untouched and having same password as in repo.

Docker engine is also running.

Anyone please suggest me what to do in the case.

Best, Ujjwal Goyal

Screenshots/recordings

No response

Superset version

master / latest-dev

Python version

3.9

Node version

16

Browser

Chrome

Additional context

No response

Checklist

  • [x] I have searched Superset docs and Slack and didn't find a solution to my problem.
  • [x] I have searched the GitHub issue tracker and didn't find a similar bug report.
  • [x] I have checked Superset's logs for errors and if I found a relevant Python stacktrace, I included it here as text in the "additional context" section.

Comment From: dosubot[bot]

The most common cause of authorization errors in the Superset Docker Compose setup is a mismatch or stale state in the database credentials or Docker volumes. Here’s what you can do:

  1. Make sure your docker/.env file is unchanged and matches the repo defaults—both POSTGRES_USER/POSTGRES_PASSWORD and DATABASE_USER/DATABASE_PASSWORD should be set to superset cite.
  2. If you’ve run Superset before, persistent Docker volumes from an older Postgres version or previous runs can cause authentication errors. Run: docker compose -f docker-compose-image-tag.yml down -v docker compose -f docker-compose-image-tag.yml up This will clear old volumes and start fresh cite.
  3. If you still can’t log in with admin/admin, the database might not have been initialized or the admin user wasn’t created. Enter the running superset container and run: superset fab create-admin superset db upgrade superset init This ensures the admin user and DB schema are set up cite.
  4. Always check the logs of both the db and superset containers for more detailed error messages—they often reveal the root cause.

Recent changes to the repo have renamed and clarified docker-compose file usage, so make sure you’re using docker-compose-image-tag.yml as documented cite.

If you have any custom config overrides (like superset_config_docker.py or .env-local), double-check that they don’t introduce mismatches.

If the problem persists, sharing the relevant error logs from the db and superset containers will help pinpoint the issue.

To reply, just mention @dosu.

How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other  Join Discord Share on X

Comment From: UjjwalGoyal1113

I have verified points 1,2. For point 3 superset container should be running but in my case container is not running it throws the authorization error whenever i tired to run it.

Comment From: rusackas

It looks like you're using Windows, which is currently unsupported.