Kwazao commented on issue #24685: URL: https://github.com/apache/superset/issues/24685#issuecomment-1635994688
> * `TAG=2.1.0 docker-compose -f docker-compose-non-dev.yml up` Hi, I still face the same login problem with V 2.1.0, even after trying multiple configurations with CSRF config / WEBDRIVER URL... Here is my thought process on trying to resolve this issue : - When i look at the logs it seems to be related to #20319 and the last comment from @sherlock30 implies a missed build in superset-frontend. But I don't see how to fix that inside a running/paused container (npm is not installed in superset_init images). I tried to rebuild images from scratch but it keeps crashing my VM. - In an other attempt I tried to isolate the issue and the docker image for superset seems to work fine with this very simple config (2.1.1rc1 not to use in prod,): Debian 10 Superset 2.1.1rc1 (work with 2.1.0 too) Dockerfile ```Dockerfile FROM apache/superset:2.1.1rc1 # passing SECRET_KEY for docker-compose use ARG SUPERSET_SECRET_KEY ENV SUPERSET_SECRET_KEY=$SUPERSET_SECRET_KEY # Switching to root to install the required packages USER root # as suggested in the dockerhub doc RUN pip install mysqlclient RUN pip install psycopg2 RUN pip install sqlalchemy # Switching back to using the `superset` user USER superset RUN superset fab create-admin \ --username admin \ --firstname Superset \ --lastname Admin \ --email [email protected] \ --password <youradminpassword> RUN superset db upgrade RUN superset init RUN superset load_examples WORKDIR /app CMD ["/bin/sh","-c","/usr/bin/run-server.sh"] ``` docker-compose.yml ``` YAML x-superset-depends-on: &superset-depends-on - db x-superset-volumes: &superset-volumes # /app/pythonpath_docker will be appended to the PYTHONPATH in the final container - ./docker:/app/docker - superset_home:/app/superset_home version: "3.7" services: db: env_file: .env image: postgres:14 container_name: superset_db restart: unless-stopped volumes: - db_home:/var/lib/postgresql/data superset: build: context: . args: SUPERSET_SECRET_KEY: '<secret-key>' dockerfile: Dockerfile container_name: superset_app user: "root" restart: unless-stopped ports: - 8088:8088 depends_on: *superset-depends-on volumes: *superset-volumes volumes: superset_home: external: false db_home: external: false ``` So, right know I don't know if there is a hope for this issue to be fixed and have a decent production stack or if I need to rebuild myself a complete docker-compose.yml, step-by-step... Any thoughts ? -- This is an automated message from the Apache Git Service. To respond to the message, please log on to GitHub and use the URL above to go to the specific comment. To unsubscribe, e-mail: [email protected] For queries about this service, please contact Infrastructure at: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
