dosubot[bot]
commented
3 months ago @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:
-
Ensure the
.envfile is properly configured:- Create a
docker/.envfile with your unique random secure passwords andSECRET_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
- Create a
-
Update the
docker-compose-non-dev.ymlfile:- Ensure the
env_fileentries 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
- Ensure the
-
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
- Run the following command to start the services defined in
-
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
- Run the following command to initialize the database and create an admin user:
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.
matsvitt
Bug description
Hi there,
I tried to spin up the prod version with docker-compose-non-dev.yml from the current master branch and get two problems: The call
docker compose -f docker-compose-non-dev.yml up -d
results in the error: _validating docker-compose-non-dev.yml: services.db.envfile.0 must be a string
So I changed the env file entries on the docker-compose file to:
_envfile: ./docker/.env-non-dev
The the spin up works however when I try to create a new admin user using
_docker exec supersetapp superset fab create-admin
I see that the database connection is refused? The reason seems to be that the docker/.env file sets _DATABASEHOST = db. However the database service “db” defined inside the docker-compose-non-dev.yml is set to superset_db. After I adjusted the entry in docker/.env to
_DATABASE_HOST=supersetdb
the superset service works fine. Did I miss anything in order to prepare the spinup for production? Did I overlook anything?
How to reproduce the bug
Screenshots/recordings
The startup of the prod service using docker compose -f docker-compose-non-dev.yml gives this error:
validating docker-compose-non-dev.yml: services.db.env_file.0 must be a string
Upon the creation of a new admin user the error is:
2024-06-19 16:37:17,703:DEBUG:superset.utils.logging_configurator:logging was configured successfully 2024-06-19 16:37:17,718:ERROR:flask_appbuilder.security.sqla.manager:DB Creation and initialization failed: (psycopg2.OperationalError) connection to server at "db" (10.0.1.231), port 5432 failed: FATAL: password authentication failed for user "superset"
Superset version
master / latest-dev
Python version
Not applicable
Node version
Not applicable
Browser
Not applicable
Additional context
No response
Checklist