start of production no possible due to errors in docker-compose-non-dev.yml and docker/.env about superset HOT 3 OPEN

@matsvitt Hello there! I'm here to help you with any bugs, questions, or contributions you have. Just give me a shout, and I'll do my best to assist you while we wait for a human maintainer.

To address the issues you're encountering with the docker-compose-non-dev.yml and docker/.env files, follow these steps:

1. Ensure the .env file is properly configured:

   • Create a docker/.env file with your unique random secure passwords and SECRET_KEY.
   • Example content for docker/.env:

     POSTGRES_DB=superset
     POSTGRES_USER=superset
     POSTGRES_PASSWORD=your_postgres_password
     SECRET_KEY=your_secret_key
     DATABASE_HOST=superset_db

2. Update the docker-compose-non-dev.yml file:

   • Ensure the env_file entries are correctly specified as strings.
   • Example docker-compose-non-dev.yml:

     version: "4.0"
     services:
       redis:
         image: redis:7
         container_name: superset_cache
         restart: unless-stopped
         volumes:
           - redis:/data
     
       db:
         env_file:
           - ./docker/.env
         image: postgres:15
         container_name: superset_db
         restart: unless-stopped
         volumes:
           - db_home:/var/lib/postgresql/data
           - ./docker/docker-entrypoint-initdb.d:/docker-entrypoint-initdb.d
     
       superset:
         env_file:
           - ./docker/.env
         build:
           context: .
           target: dev
           cache_from:
             - apache/superset-cache:3.10-slim-bookworm
         container_name: superset_app
         command: ["/app/docker/docker-bootstrap.sh", "app-gunicorn"]
         user: "root"
         restart: unless-stopped
         ports:
           - 8088:8088
         depends_on:
           - db
           - redis
         volumes:
           - ./docker:/app/docker
           - superset_home:/app/superset_home
     
       superset-init:
         container_name: superset_init
         build:
           context: .
           target: dev
           cache_from:
             - apache/superset-cache:3.10-slim-bookworm
         command: ["/app/docker/docker-init.sh"]
         env_file:
           - ./docker/.env
         depends_on:
           - db
           - redis
         user: "root"
         volumes:
           - ./docker:/app/docker
           - superset_home:/app/superset_home
         healthcheck:
           disable: true
     
       superset-worker:
         build:
           context: .
           target: dev
           cache_from:
             - apache/superset-cache:3.10-slim-bookworm
         container_name: superset_worker
         command: ["/app/docker/docker-bootstrap.sh", "worker"]
         env_file:
           - ./docker/.env
         restart: unless-stopped
         depends_on:
           - db
           - redis
         user: "root"
         volumes:
           - ./docker:/app/docker
           - superset_home:/app/superset_home
         healthcheck:
           test:
             [
               "CMD-SHELL",
               "celery -A superset.tasks.celery_app:app inspect ping -d celery@$$HOSTNAME",
             ]
     
       superset-worker-beat:
         build:
           context: .
           target: dev
           cache_from:
             - apache/superset-cache:3.10-slim-bookworm
         container_name: superset_worker_beat
         command: ["/app/docker/docker-bootstrap.sh", "beat"]
         env_file:
           - ./docker/.env
         restart: unless-stopped
         depends_on:
           - db
           - redis
         user: "root"
         volumes:
           - ./docker:/app/docker
           - superset_home:/app/superset_home
         healthcheck:
           disable: true
     
     volumes:
       superset_home:
         external: false
       db_home:
         external: false
       redis:
         external: false

3. Start the services:

   • Run the following command to start the services defined in docker-compose-non-dev.yml:

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

4. Initialize the database and create an admin user:

   • Run the following command to initialize the database and create an admin user:

     docker-compose -f docker-compose-non-dev.yml run --rm superset-init

By following these steps, you should be able to spin up the production version and create an admin user without encountering errors related to the env_file and database connection ^[1].

To continue talking to Dosu, mention @dosu.

from superset.

Yes, it would be correct to create a pull request to address the issues in the docker-compose-non-dev.yml and docker/.env files in the master branch ^[1].

To continue talking to Dosu, mention @dosu.

from superset.

from superset.