superset-init won't go up

[FrancescoCastaldi]

Hi, I'm experiencing an issue with superset-init that gets stuck in a loop at:

Built apache-superset-core @ file:///app/superset-core
Prepared 1 package in 19.62s
Uninstalled 1 package in 17ms
Installed 1 package in 7ms
~ apache-superset-core==0.1.0rc1 (from file:///app/superset-core)
Reinstalling the app in editable mode

It doesn't proceed further after running build and compose up -d. How can I resolve this?

[dosubot[bot]]

Hi @FrancescoCastaldi! I'm Dosu and I’m helping the superset team.

This is a known issue, usually caused by a version mismatch between your Git branch and the Docker image. When using docker-compose-image-tag.yml, your local docker/ folder gets mounted and overrides the container's entrypoints. If you're on master or latest-dev branch but using an older image tag, the bootstrap script may reference tools (like uv) that don't exist in the older image, causing the loop.

Recommended fixes:

1. Match your Git branch to the image version:

   git fetch --tags
   git checkout 4.1.1  # or whatever version you're targeting
   docker compose -f docker-compose-image-tag.yml up

2. Or use the non-dev compose file which avoids these mount issues:

   docker compose -f docker-compose-non-dev.yml up

3. If the above don't help, try a complete reset to clear any stale volume data:

   docker compose down -v && docker compose up

Which compose file are you currently using, and which Superset version/branch are you on?

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[FrancescoCastaldi]

vr. 6.0.0

[dosubot[bot]]

Version 6.0.0 has some known Docker initialization issues. Since you're using the default docker-compose.yml which mounts your local code, make sure your Git checkout matches:

git fetch --tags
git checkout 6.0.0

Then try:

docker compose down
docker compose build --no-cache
docker compose up -d

If that still loops, check the init logs to see what's happening:

docker compose logs -f superset-init

This will show you the actual error. The "Reinstalling the app in editable mode" message is normal — the issue is likely what happens (or doesn't happen) after that step. Can you share the full log output from superset-init?

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[FrancescoCastaldi]

Building Superset frontend in dev mode inside docker container

npm error code ENOTEMPTY

npm error syscall rename

npm error path /app/superset-frontend/packages/generator-superset/node_modules/fs-extra

npm error dest /app/superset-frontend/packages/generator-superset/node_modules/.fs-extra-noNkzu9G

npm error errno -39

npm error ENOTEMPTY: directory not empty, rename '/app/superset-frontend/packages/generator-superset/node_modules/fs-extra' -> '/app/superset-frontend/packages/generator-superset/node_modules/.fs-extra-noNkzu9G'

npm notice

npm notice New major version of npm available! 10.8.2 -> 11.12.0

npm notice Changelog: https://github.com/npm/cli/releases/tag/v11.12.0

npm notice To update run: npm install -g npm@11.12.0

npm notice

npm error A complete log of this run can be found in: /root/.npm/_logs/2026-03-24T11_21_25_394Z-debug-0.log

Running

npm error code ENOTEMPTY

npm error syscall rename

npm error path /app/superset-frontend/plugins/legacy-plugin-chart-calendar/node_modules/d3-array

npm error dest /app/superset-frontend/plugins/legacy-plugin-chart-calendar/node_modules/.d3-array-ZX6oKuyo

npm error errno -39

npm error ENOTEMPTY: directory not empty, rename '/app/superset-frontend/plugins/legacy-plugin-chart-calendar/node_modules/d3-array' -> '/app/superset-frontend/plugins/legacy-plugin-chart-calendar/node_modules/.d3-array-ZX6oKuyo'

npm error A complete log of this run can be found in: /root/.npm/_logs/2026-03-24T11_21_34_510Z-debug-0.log

[dosubot[bot]]

This ENOTEMPTY error is a known issue caused by residual Docker volumes conflicting with npm's rename operations during install.

Try these fixes in order:

1. Clear Docker volumes completely:

   docker compose down -v
   docker system prune --volumes
   docker compose up --build

2. If that doesn't work, enable npm prune mode:

   export NPM_RUN_PRUNE=true
   docker compose up

   This triggers a full cleanup of node_modules before running npm install.

3. Fallback — build frontend locally instead of in Docker:
   Set BUILD_SUPERSET_FRONTEND_IN_DOCKER=false in your .env file, then run npm install and npm run dev directly on your host machine.

Let us know if any of these help!

To reply, just mention @dosu.

---

^{How did I do? Good | Irrelevant | Incorrect | Verbose | Hallucination | Report 🐛 | Other}

   

[FrancescoCastaldi]

not working llm boy