GitHub user yudin-s added a comment to the discussion: OCI Error
That error means Docker started a Superset container with a command that points to this file: ```text /app/docker/docker-init.sh ``` but that file is not inside the container at runtime. In the Superset development compose files, `/app/docker` normally comes from this bind mount: ```yaml ./docker:/app/docker ``` So the usual causes are: 1. you are not running `docker compose` from the root of a full Superset git checkout; 2. the local `docker/` folder is missing or incomplete; 3. you mixed a compose file from the source repo with a prebuilt image/setup that does not include those repo files. Check this on the machine where you run compose: ```bash pwd ls -la docker/docker-init.sh docker compose config | grep -A5 -B5 '/app/docker' ``` If `docker/docker-init.sh` does not exist locally, clone/download the full Superset repository again and run compose from that repository root. If you only want to run Superset as an application rather than develop Superset itself, do not use a source-tree compose file that expects `./docker:/app/docker`. Use the install path from the Superset docs for your target environment, or make sure your compose file and image come from the same Superset version. If this solves it, please mark this comment as the answer so other people can find it faster. GitHub link: https://github.com/apache/superset/discussions/40427#discussioncomment-17072095 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
