# I cannot deploy docker-taiga-back-1 via docker compose **URL:** \ **Category:** Self hosted Taiga\ **Tags:** docker\ **Created:** [October 9, 2023, 11:59am UTC](https://community.taiga.io/t/i-cannot-deploy-docker-taiga-back-1-via-docker-compose/1961 "2023-10-09T11:59:47Z")\ **Posts on this page:** 8\ **Page:** 1
**Author:** ![atlet99](https://avatars.discourse-cdn.com/v4/letter/a/258eb7/32.png) [@atlet99](https://community.taiga.io/u/atlet99)\ **Post date:** [October 9, 2023, 11:59am UTC](https://community.taiga.io/t/i-cannot-deploy-docker-taiga-back-1-via-docker-compose/1961/1 "2023-10-09T11:59:47Z")
When I build docker compose file, I got error below. Tell me how to fix this? * * * CentOS 8 Docker: 23.1 * * * ```auto docker-taiga-back-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ docker-taiga-back-1 | File "/opt/venv/lib/python3.11/site-packages/psycopg2/ __init__.py", line 122, in connect docker-taiga-back-1 | conn = _connect(dsn, connection_factory=connection_factory, **kwasync) docker-taiga-back-1 | ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ docker-taiga-back-1 | django.db.utils.OperationalError: connection to server on socket "/var/run/postgresql/.s.PGSQL.5432" failed: No such file or directory docker-taiga-back-1 | Is the server running locally and accepting connections on that socket? docker-taiga-back-1 | docker-taiga-back-1 exited with code 1 ``` ---
**Author:** ![tdelatorre](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/tdelatorre/32/519_2.png) [@tdelatorre](https://community.taiga.io/u/tdelatorre)\ **Post date:** [October 11, 2023, 8:46am UTC](https://community.taiga.io/t/i-cannot-deploy-docker-taiga-back-1-via-docker-compose/1961/2 "2023-10-11T08:46:19Z")
Hi @atlet99 Welcome to our community! In order to help you, we need: - check the logs `docker logs -f` to see if there is more information. - your docker-compose.yml (redacted without sensitive data) - the result of `docker-compose ps` Regards. ---
**Author:** ![atlet99](https://avatars.discourse-cdn.com/v4/letter/a/258eb7/32.png) [@atlet99](https://community.taiga.io/u/atlet99)\ **Post date:** [October 11, 2023, 10:30am UTC](https://community.taiga.io/t/i-cannot-deploy-docker-taiga-back-1-via-docker-compose/1961/3 "2023-10-11T10:30:03Z")
Hi @tdelatorre Thank you for your feedback. Yes, I would like to say, but I don’t know where to begin… _ **docker logs -f** _ taigaio/taiga-back:latest ```auto File "/opt/venv/lib/python3.11/site-packages/django/db/models/base.py", line 1303, in check *cls._check_indexes(databases), ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/db/models/base.py", line 1695, in _check_indexes connection.features.supports_covering_indexes or ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/utils/functional.py", line 48, in __get__ res = instance. __dict__ [self.name] = self.func(instance) ^^^^^^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/db/backends/postgresql/features.py", line 92, in is_postgresql_11 return self.connection.pg_version >= 110000 ^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/utils/functional.py", line 48, in __get__ res = instance. __dict__ [self.name] = self.func(instance) ^^^^^^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/db/backends/postgresql/base.py", line 329, in pg_version with self.temporary_connection(): File "/usr/local/lib/python3.11/contextlib.py", line 137, in __enter__ return next(self.gen) ^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/db/backends/base/base.py", line 603, in temporary_connection with self.cursor() as cursor: ^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/utils/asyncio.py", line 33, in inner return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/db/backends/base/base.py", line 259, in cursor return self._cursor() ^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/db/backends/base/base.py", line 235, in _cursor self.ensure_connection() File "/opt/venv/lib/python3.11/site-packages/django/utils/asyncio.py", line 33, in inner return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/db/backends/base/base.py", line 218, in ensure_connection with self.wrap_database_errors: File "/opt/venv/lib/python3.11/site-packages/django/db/utils.py", line 90, in __exit__ raise dj_exc_value.with_traceback(traceback) from exc_value File "/opt/venv/lib/python3.11/site-packages/django/db/backends/base/base.py", line 219, in ensure_connection self.connect() File "/opt/venv/lib/python3.11/site-packages/django/utils/asyncio.py", line 33, in inner return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/db/backends/base/base.py", line 200, in connect self.connection = self.get_new_connection(conn_params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/utils/asyncio.py", line 33, in inner return func(*args, **kwargs) ^^^^^^^^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/django/db/backends/postgresql/base.py", line 187, in get_new_connection connection = Database.connect(**conn_params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/psycopg2/ __init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ django.db.utils.OperationalError: connection to server at "taiga-db" (172.24.0.3), port 5432 failed: FATAL: password authentication failed for user "taiga" ``` So, I attached pictures ![docker_compose_ps](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/2X/9/9926a576c75df8d3844625ab893cd261fe0d635b.png) ![docker_compose_ps_a](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/2X/3/3f7c1f60a804dc62952d40d00f535636a3a73ff8.png) below config _docker-compose.yml_ ```auto version: "3.5" x-environment: &default-back-environment # These environment variables will be used by taiga-back and taiga-async. # Database settings POSTGRES_DB: "taiga" POSTGRES_USER: "${POSTGRES_USER}" POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}" POSTGRES_HOST: "taiga-db" # Taiga settings TAIGA_SECRET_KEY: "${SECRET_KEY}" TAIGA_SITES_SCHEME: "${TAIGA_SCHEME}" TAIGA_SITES_DOMAIN: "${TAIGA_DOMAIN}" TAIGA_SUBPATH: "${SUBPATH}" # Email settings. EMAIL_BACKEND: "django.core.mail.backends.${EMAIL_BACKEND}.EmailBackend" DEFAULT_FROM_EMAIL: "${EMAIL_DEFAULT_FROM}" EMAIL_USE_TLS: "${EMAIL_USE_TLS}" EMAIL_USE_SSL: "${EMAIL_USE_SSL}" EMAIL_HOST: "${EMAIL_HOST}" EMAIL_PORT: "${EMAIL_PORT}" EMAIL_HOST_USER: "${EMAIL_HOST_USER}" EMAIL_HOST_PASSWORD: "${EMAIL_HOST_PASSWORD}" # Rabbitmq settings RABBITMQ_USER: "${RABBITMQ_USER}" RABBITMQ_PASS: "${RABBITMQ_PASS}" # Telemetry settings ENABLE_TELEMETRY: "${ENABLE_TELEMETRY}" # ...your customizations go here x-volumes: &default-back-volumes # These volumens will be used by taiga-back and taiga-async. - taiga-static-data:/taiga-back/static - taiga-media-data:/taiga-back/media # - ./config.py:/taiga-back/settings/config.py services: taiga-db: image: postgres:12.3 environment: POSTGRES_DB: "taiga" POSTGRES_USER: "${POSTGRES_USER}" POSTGRES_PASSWORD: "${POSTGRES_PASSWORD}" healthcheck: test: ["CMD-SHELL", "pg_isready -U ${POSTGRES_USER}"] interval: 2s timeout: 15s retries: 5 start_period: 3s volumes: - taiga-db-data:/var/lib/postgresql/data networks: - taiga taiga-back: image: taigaio/taiga-back:latest environment: *default-back-environment volumes: *default-back-volumes networks: - taiga depends_on: taiga-db: condition: service_healthy taiga-events-rabbitmq: condition: service_started taiga-async-rabbitmq: condition: service_started taiga-async: image: taigaio/taiga-back:latest entrypoint: ["/taiga-back/docker/async_entrypoint.sh"] environment: *default-back-environment volumes: *default-back-volumes networks: - taiga depends_on: taiga-db: condition: service_healthy taiga-events-rabbitmq: condition: service_started taiga-async-rabbitmq: condition: service_started taiga-async-rabbitmq: image: rabbitmq:3.8-management-alpine environment: RABBITMQ_ERLANG_COOKIE: "${RABBITMQ_ERLANG_COOKIE}" RABBITMQ_DEFAULT_USER: "${RABBITMQ_USER}" RABBITMQ_DEFAULT_PASS: "${RABBITMQ_PASS}" RABBITMQ_DEFAULT_VHOST: "${RABBITMQ_VHOST}" hostname: "taiga-async-rabbitmq" volumes: - taiga-async-rabbitmq-data:/var/lib/rabbitmq networks: - taiga taiga-front: image: taigaio/taiga-front:latest environment: TAIGA_URL: "${TAIGA_SCHEME}://${TAIGA_DOMAIN}" TAIGA_WEBSOCKETS_URL: "${WEBSOCKETS_SCHEME}://${TAIGA_DOMAIN}" TAIGA_SUBPATH: "${SUBPATH}" # ...your customizations go here networks: - taiga # volumes: # - ./conf.json:/usr/share/nginx/html/conf.json taiga-events: image: taigaio/taiga-events:latest environment: RABBITMQ_USER: "${RABBITMQ_USER}" RABBITMQ_PASS: "${RABBITMQ_PASS}" TAIGA_SECRET_KEY: "${SECRET_KEY}" networks: - taiga depends_on: taiga-events-rabbitmq: condition: service_started taiga-events-rabbitmq: image: rabbitmq:3.8-management-alpine environment: RABBITMQ_ERLANG_COOKIE: "${RABBITMQ_ERLANG_COOKIE}" RABBITMQ_DEFAULT_USER: "${RABBITMQ_USER}" RABBITMQ_DEFAULT_PASS: "${RABBITMQ_PASS}" RABBITMQ_DEFAULT_VHOST: "${RABBITMQ_VHOST}" hostname: "taiga-events-rabbitmq" volumes: - taiga-events-rabbitmq-data:/var/lib/rabbitmq networks: - taiga taiga-protected: image: taigaio/taiga-protected:latest environment: MAX_AGE: "${ATTACHMENTS_MAX_AGE}" SECRET_KEY: "${SECRET_KEY}" networks: - taiga taiga-gateway: image: nginx:1.19-alpine ports: - "9000:80" volumes: - ./taiga-gateway/taiga.conf:/etc/nginx/conf.d/default.conf - taiga-static-data:/taiga/static - taiga-media-data:/taiga/media networks: - taiga depends_on: - taiga-front - taiga-back - taiga-events volumes: taiga-static-data: taiga-media-data: taiga-db-data: taiga-async-rabbitmq-data: taiga-events-rabbitmq-data: networks: taiga: ``` ---
**Author:** ![tdelatorre](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/tdelatorre/32/519_2.png) [@tdelatorre](https://community.taiga.io/u/tdelatorre)\ **Post date:** [October 13, 2023, 6:34am UTC](https://community.taiga.io/t/i-cannot-deploy-docker-taiga-back-1-via-docker-compose/1961/4 "2023-10-13T06:34:19Z")
Hi @atlet99 According to your logs it seems like a database connection problem: ```auto File "/opt/venv/lib/python3.11/site-packages/django/db/backends/postgresql/base.py", line 187, in get_new_connection connection = Database.connect(**conn_params) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ File "/opt/venv/lib/python3.11/site-packages/psycopg2/ __init__.py", line 122, in connect conn = _connect(dsn, connection_factory=connection_factory, **kwasync) ^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^ django.db.utils.OperationalError: connection to server at "taiga-db" (172.24.0.3), port 5432 failed: FATAL: password authentication failed for user "taiga" ``` Check that the database configuration variables in your `.env` file have the correct values for the **taiga** database user (following [https://community.taiga.io/t/taiga-30min-setup/170#database-settings-7](https://community.taiga.io/t/taiga-30min-setup/170#database-settings-7)) If this is not your first time deploying Taiga and you were already using taiga-docker I recommend that you follow this [migration guide](https://docs.taiga.io/upgrades-docker-migrate.html) to use the new `.env` based deployment (Taiga version 6.6.0+) I hope this helps. Regards. ---
**Author:** ![atlet99](https://avatars.discourse-cdn.com/v4/letter/a/258eb7/32.png) [@atlet99](https://community.taiga.io/u/atlet99)\ **Post date:** [October 16, 2023, 6:50am UTC](https://community.taiga.io/t/i-cannot-deploy-docker-taiga-back-1-via-docker-compose/1961/5 "2023-10-16T06:50:45Z")
Hello @tdelatorre Thank you for your advice. I try checked my problem, but do not find worked solutions. So, I deploy taiga docker-compose.yml without changes, because I tested in my new, test-env server. My server: `Oracle Linux Server 8.7` Kernel version: ```auto 5.4.17-2136.316.7.el8uek.x86_64 ``` My docker version: ```auto Client: Docker Engine - Community Version: 23.0.1 API version: 1.42 Go version: go1.19.5 Git commit: a5ee5b1 Built: Thu Feb 9 19:49:07 2023 OS/Arch: linux/amd64 Context: default Server: Docker Engine - Community Engine: Version: 23.0.1 API version: 1.42 (minimum version 1.12) Go version: go1.19.5 Git commit: bc3805a Built: Thu Feb 9 19:46:47 2023 OS/Arch: linux/amd64 Experimental: false containerd: Version: 1.6.18 GitCommit: 2456e983eb9e37e47538f59ea18f2043c9a73640 runc: Version: 1.1.4 GitCommit: v1.1.4-0-g5fd4c4d docker-init: Version: 0.19.0 GitCommit: de40ad0 ``` Also, I fetched latest changes from main branche and pulled, If changes will confirmed: ```auto Already up to date. ``` ---
**Author:** ![daniel.herrero](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/daniel.herrero/32/301_2.png) [@daniel.herrero](https://community.taiga.io/u/daniel.herrero)\ **Post date:** [October 31, 2023, 11:20am UTC](https://community.taiga.io/t/i-cannot-deploy-docker-taiga-back-1-via-docker-compose/1961/6 "2023-10-31T11:20:02Z")
It seems like a problem with the values of the POSTGRES\_XXX variables (POSTGRES\_DB, POSTGRES\_USER , POSTGRES\_PASSWORD) that `taiga-back` is using to connect the `taiga-db` service. They are read in the `docker-compose.yml` from the `.env` file. Could it be dirty data from an old installation? You can perhaps trying to delete the volume for the `taiga-db` service : ```auto daniel ~/projects/taiga-docker [main] $ docker compose down daniel ~/projects/taiga-docker [main] $ docker volume ls DRIVER VOLUME NAME local 5ceafaf9a24f20b9ecc364e93bbf5345ee30b6d8f048c0f2fe1b1fc97c0d90a8 local taiga-docker_penpot_assets_data local taiga-docker_penpot_postgres_data local taiga-docker_taiga-async-rabbitmq-data local taiga-docker_taiga-db-data local taiga-docker_taiga-events-rabbitmq-data local taiga-docker_taiga-media-data local taiga-docker_taiga-static-data daniel ~/projects/taiga-docker [main] $ docker volume rm taiga-docker_taiga-db-data taiga-docker_taiga-db-data ``` Then you could start with `$ ./launch-taiga.sh` to allow recreating the database. ---
**Author:** ![atlet99](https://avatars.discourse-cdn.com/v4/letter/a/258eb7/32.png) [@atlet99](https://community.taiga.io/u/atlet99)\ **Post date:** [November 1, 2023, 5:27am UTC](https://community.taiga.io/t/i-cannot-deploy-docker-taiga-back-1-via-docker-compose/1961/7 "2023-11-01T05:27:41Z")
Thank you so much, @daniel.herrero But today, I have _ **new problem** _: ![taiga_error](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/2X/5/52bf9a2c5181ebad81a77ea2d91daab3c0f535fa.png) Also, all of containers in state _“up/running”_. ![taiga_stats](https://europe1.discourse-cdn.com/flex017/uploads/taiga/original/2X/7/7b43df4f098e7f593d56b8653c909038493c516b.png) So, what can I do with it ? ---
**Author:** ![daniel.herrero](https://dub1.discourse-cdn.com/flex017/user_avatar/community.taiga.io/daniel.herrero/32/301_2.png) [@daniel.herrero](https://community.taiga.io/u/daniel.herrero)\ **Post date:** [November 2, 2023, 6:16am UTC](https://community.taiga.io/t/i-cannot-deploy-docker-taiga-back-1-via-docker-compose/1961/8 "2023-11-02T06:16:18Z")
> [@daniel.herrero](#): > > ? You can perhaps trying to delete the volume for the `taiga-db` Hi @atlet99, In order to let the community help you you need to provide more context. When did it happen? What error do you have in taiga-back service? Any problem in the logs when starting up? Thanks