Giter VIP home page Giter VIP logo

Comments (6)

lubo avatar lubo commented on September 25, 2024

Hi. I don't think ~ is a valid value for UWSGI_HTTP. See uWSGI Options.

from docker-taiga.

Sawrz avatar Sawrz commented on September 25, 2024

In your docker-compose file you use ~. Maybe it's worth to change it there?

However, I removed the UWSGI_HTTP environment parameter entirely, but I get the same error message as before.

from docker-taiga.

lubo avatar lubo commented on September 25, 2024

In YAML, ~ is equivalent to null. So, UWSGI_HTTP: ~ just unsets UWSGI_HTTP. Could you provide your whole compose file?

from docker-taiga.

Sawrz avatar Sawrz commented on September 25, 2024

Ah ok! I didn't knew that. The thing is I moved from docker compose to portainer. Unfortunately they support docker-compose only on version 2.
So I had to translate my old compose file to docker. Here you'll find the configuration overview.

I used a combination of my docker-compose file and the updates you made within the last 3 monts. The content:

version: "3.7"

x-taiga-common: &taiga-common
  image: devinsolutions/taiga:5.0.10
  volumes:
    - type: bind
      source: /share/cloud_services/taiga/media
      target: /srv/taiga-back/media
    - /share/Containers/config_templates/taiga/front.json:/etc/opt/taiga-front/conf.json:ro
    - /share/Containers/config_templates/taiga/settings.py:/etc/opt/taiga-back/settings.py:ro
services:

  broker:
    image: rabbitmq:3.8
    environment:
      RABBITMQ_DEFAULT_VHOST: taiga
      RABBITMQ_NODENAME: rabbit@localhost
    volumes:
      - broker:/var/lib/rabbitmq
    networks:
      - backend

  database:
    image: postgres:11
    environment:
      POSTGRES_DB: DB_NAME
      POSTGRES_PASSWORD: PASSWORD
      POSTGRES_USER: USER
    stop_signal: SIGINT
    volumes:
      - type: bind
        source: /share/cloud_services/taiga/db
        target: /var/lib/postgresql/data
    networks:
      - backend

  events:
    image: devinsolutions/taiga-events:latest
    deploy:
      replicas: 1
      update_config:
        order: start-first
    healthcheck:
      interval: 5s
      # Taiga-events seems unable to reconnect to message broker when connection cannot be
      # established or is closed. There also does not seem to be another way to tell if the server
      # is actually able to communicate with the broker.
      test: "wget -q -t 1 http://localhost:8080 2>&1 | grep -q '426 Upgrade Required' &&
        ! egrep -m 1 -q '^Unhandled rejection ' /var/log/taiga-events.log"
    volumes:
      - /share/Containers/config_templates/taiga/events.json:/etc/opt/taiga-events/config.json:ro
    networks:
      - backend

  migrations:
    <<: *taiga-common
    command:
      - migrate
      # Make sure this command is run only during the initial setup as it will
      # overwrite existing data.
      # - populate-db
    deploy:
      restart_policy:
        condition: on-failure
        delay: 5s
    networks:
      - backend


    

  server:
    <<: *taiga-common
    command: run-server
    deploy:
      replicas: 1
      update_config:
        order: start-first
    environment:
      UWSGI_HTTP: ~
      UWSGI_HTTP_SOCKET: :8080
      UWSGI_OFFLOAD_THREADS: 4
      UWSGI_UWSGI_SOCKET: :3031
    healthcheck:
      test: wget -q -t 1 --spider http://localhost:8080/api/v1/
    stop_signal: SIGHUP
    environment:
      - VIRTUAL_HOST= URL
      - LETSENCRYPT_HOST= URL
    networks:
      - backend
      - reverse_proxy

volumes:
  broker:

networks:
  backend:
    name: taiga_backend
  reverse_proxy:
    external: true

from docker-taiga.

lubo avatar lubo commented on September 25, 2024

I can reproduce the behavior when I remove the leading colon in UWSGI_HTTP_SOCKET or UWSGI_UWSGI_SOCKET as you have in the original message and on the screenshot you've provided. Without the leading colon, the values aren't valid socket addresses and they're therefore treated as file names. Since uWSGI can't create these files in the working directory, it cannot bind to them.

from docker-taiga.

Sawrz avatar Sawrz commented on September 25, 2024

I can confirm - it's working right now. I removed all UWSGI variables, restarted, and it works fine. So, thank you for your help!

from docker-taiga.

Related Issues (10)

Recommend Projects

  • React photo React

    A declarative, efficient, and flexible JavaScript library for building user interfaces.

  • Vue.js photo Vue.js

    🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.

  • Typescript photo Typescript

    TypeScript is a superset of JavaScript that compiles to clean JavaScript output.

  • TensorFlow photo TensorFlow

    An Open Source Machine Learning Framework for Everyone

  • Django photo Django

    The Web framework for perfectionists with deadlines.

  • D3 photo D3

    Bring data to life with SVG, Canvas and HTML. 📊📈🎉

Recommend Topics

  • javascript

    JavaScript (JS) is a lightweight interpreted programming language with first-class functions.

  • web

    Some thing interesting about web. New door for the world.

  • server

    A server is a program made to process requests and deliver data to clients.

  • Machine learning

    Machine learning is a way of modeling and interpreting data that allows a piece of software to respond intelligently.

  • Game

    Some thing interesting about game, make everyone happy.

Recommend Org

  • Facebook photo Facebook

    We are working to build community through open source technology. NB: members must have two-factor auth.

  • Microsoft photo Microsoft

    Open source projects and samples from Microsoft.

  • Google photo Google

    Google ❤️ Open Source for everyone.

  • D3 photo D3

    Data-Driven Documents codes.