Impossible to run dev-server

[DuyAnhBD-PTIT]

I have tried several solutions to no avail, docker compose just seems to fail at npm run build with no error logs, I have tried to switching to a computer with higher specs but same problem occur. Is there a way to workaround this via pulling the readily available image and injecting my custom frontend code to the container?

[dosubot[bot]]

Yes, you can work around frontend build failures by using a pre-built Superset Docker image and injecting your custom frontend code. The standard approach is to build your custom frontend assets locally (outside Docker), then either mount them into the container or extend the image.

For development, Superset's Docker setup mounts the local superset-frontend directory into the container, allowing you to hot-reload or override the frontend code. If you want to inject built assets into a running container or a pre-built image, you can do this by either:

• Mounting your local build output (the built static files) into the appropriate directory inside the container using a Docker volume.
• Creating a custom Dockerfile that starts FROM the official Superset image, then copies your built frontend assets into the correct location.

This method requires you to build the frontend assets on your host machine (using npm run build in superset-frontend), then either mount or copy the resulting files into the container. This is a common workaround when the in-container build fails, and it is supported by the way Superset's Docker Compose and Dockerfiles are structured. There is no official documentation for this exact workflow, but it is the standard practice for customizing the frontend in containerized deployments. See more details in this discussion and docker-compose.yml.

To reply, just mention @dosu.

---

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

[DuyAnhBD-PTIT]

@dosu You are cross-referencing my own post, whose problem has yet to be fixed. Has this method been proven successful?