Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Superset Fails to Start in Docker with Missing /app/docker/docker-bootstrap.sh Error #23484

Closed
brownie1 opened this issue Mar 24, 2023 · 9 comments
Labels
#bug Bug report

Comments

@brownie1
Copy link

Following the instructions here: https://superset.apache.org/docs/installation/installing-superset-using-docker-compose/ Superset errors out with the following error:

Attaching to superset_app, superset_cache, superset_db, superset_init, superset_worker, superset_worker_beat
Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/app/docker/docker-bootstrap.sh": stat /app/docker/docker-bootstrap.sh: no such file or directory: unknown

MacOS Version: Ventura 13.2.1
Docker Version: Docker version 23.0.1, build a5ee5b1dfc
Docker Compose Version: Docker Compose version 2.17.0

Looking through past bug reports I have seen similar issues, but nothing that fixes this issue.

@brownie1 brownie1 added the #bug Bug report label Mar 24, 2023
@mdeshmu
Copy link
Contributor

mdeshmu commented Mar 25, 2023

Which superset version?

@nytai
Copy link
Member

nytai commented Mar 27, 2023

That file should be volume mounted into the containers. Are you running this from the base of the cloned repo?

@msen7437
Copy link

Hey there,
I am also encountering this error when i try to deploy superset with docker-compose in a google cloud engine.
I basically do exactly what is done in the docs and it works on my Linux OS (ubuntu) but not on the GCE (also ubuntu).
Here is what i did:

  1. Clone the project and cd superset
  2. Install a new docker-compose version since the default version on the GCE isn't compatible with the docker-compose file
curl -L "https://github.com/docker/compose/releases/latest/download/docker-compose-$(uname -s)-$(uname -m)" -o /usr/bin/docker-compose
chmod +x /usr/bin/docker-compose

I installed version: Docker Compose version v2.22.0
3. Running docker-compose up

Here is the output i receive:

root@my-host:/superset#  docker-compose up
[+] Building 0.0s (0/0)                                                  docker:default
[+] Running 7/7
 ✔ Network superset_default        Created                                         0.1s 
 ✔ Container superset_db           Created                                         0.1s 
 ✔ Container superset_cache        Created                                         0.1s 
 ✔ Container superset_init         Created                                         0.1s 
 ✔ Container superset_worker       Created                                         0.1s 
 ✔ Container superset_worker_beat  Created                                         0.0s 
 ✔ Container superset_app          Created                                         0.1s 
Attaching to superset_app, superset_cache, superset_db, superset_init, superset_worker, superset_worker_beat
superset_cache        | 1:C 16 Oct 2023 14:28:09.836 * oO0OoO0OoO0Oo Redis is starting oO0OoO0OoO0Oo
superset_cache        | 1:C 16 Oct 2023 14:28:09.836 * Redis version=7.2.1, bits=64, commit=00000000, modified=0, pid=1, just started
superset_cache        | 1:C 16 Oct 2023 14:28:09.836 # Warning: no config file specified, using the default config. In order to specify a config file use redis-server /path/to/redis.conf
superset_cache        | 1:M 16 Oct 2023 14:28:09.836 * monotonic clock: POSIX clock_gettime
superset_cache        | 1:M 16 Oct 2023 14:28:09.837 * Running mode=standalone, port=6379.
superset_cache        | 1:M 16 Oct 2023 14:28:09.838 * Server initialized
superset_cache        | 1:M 16 Oct 2023 14:28:09.838 * Loading RDB produced by version 7.2.1
superset_cache        | 1:M 16 Oct 2023 14:28:09.838 * RDB age 126 seconds
superset_cache        | 1:M 16 Oct 2023 14:28:09.838 * RDB memory usage when created 0.83 Mb
superset_cache        | 1:M 16 Oct 2023 14:28:09.838 * Done loading RDB, keys loaded: 0, keys expired: 0.
superset_cache        | 1:M 16 Oct 2023 14:28:09.838 * DB loaded from disk: 0.000 seconds
superset_cache        | 1:M 16 Oct 2023 14:28:09.838 * Ready to accept connections tcp
superset_db           | 
superset_db           | PostgreSQL Database directory appears to contain a database; Skipping initialization
superset_db           | 
superset_db           | 2023-10-16 14:28:09.968 UTC [1] LOG:  starting PostgreSQL 15.4 (Debian 15.4-2.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
superset_db           | 2023-10-16 14:28:09.968 UTC [1] LOG:  listening on IPv4 address "0.0.0.0", port 5432
superset_db           | 2023-10-16 14:28:09.968 UTC [1] LOG:  listening on IPv6 address "::", port 5432
superset_db           | 2023-10-16 14:28:09.975 UTC [1] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
superset_db           | 2023-10-16 14:28:09.987 UTC [29] LOG:  database system was shut down at 2023-10-16 14:26:02 UTC
superset_db           | 2023-10-16 14:28:09.997 UTC [1] LOG:  database system is ready to accept connections
Error response from daemon: failed to create shim task: OCI runtime create failed: runc create failed: unable to start container process: exec: "/app/docker/docker-bootstrap.sh": stat /app/docker/docker-bootstrap.sh: no such file or directory: unknown

I ran it as root in order to cancel out possible issues with file permissions (Only done for debugging).
It worked just fine when i tried to deploy it on thursday and friday (12th and 13th of october 2023), so the issue is also pretty new for me.
Maybe the compute engine is missing a dependency or so, but i wasn't able to solve the issue.
Im looking forward to solving and resolving my issue!
Thanks in advance!

@mrjones-plip
Copy link

I'm facing this problem myself and I believe that this comment is correct, but more specifically:

  • when you run docker compose up it uses this compose file by default
  • that compose file in turn has extensions that declare the mount as - ./docker:/app/docker
  • if this bind mount fails, you will see the errors being reported here (stat /app/docker/docker-bootstrap.sh: no such file or directory: unknown)

@mdeshmu
Copy link
Contributor

mdeshmu commented Oct 20, 2023

@sfirke this is good to close, I believe.
We already have cd superset in docs. If volume mounting is not happening for some reason, its likely not a superset issue.

@sfirke
Copy link
Member

sfirke commented Oct 20, 2023

I thought the same thing as nytai above, a user could see this error if they run docker compose up without having cloned the repo so they are missing the bash files and they then don't get mounted. And @mdeshmu I agree it seems like this is not something actionable for the Superset project. Feel free to continue troubleshooting this here, and then I'll plan to close this once activity dries up.

Heads up that @sebastianliebscher has an open PR in progress that might help with this: #25546 I believe it would eliminate the need to bound these bash files. FYI Sebastian in case this is an example of why that PR will be an improvement.

@rusackas
Copy link
Member

rusackas commented Apr 8, 2024

Seems like things have indeed dried up on this thread. Let's go ahead and close this. Much has changed in Docker-land since this Issue was last touched, but if y'all think this needs to be re-opened, we can surely do so.

@rusackas rusackas closed this as completed Apr 8, 2024
@nadersoliman
Copy link

faced the same problem mounted the volume to superset-checks

    volumes:
      - ./scripts:/app/scripts  # Add this volume mount

@NDHINE
Copy link

NDHINE commented Jan 13, 2025

I am facing the same error but still I have not come across a working solution

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
#bug Bug report
Projects
None yet
Development

No branches or pull requests

9 participants