[GH-ISSUE #2305] Docker install fails on init - ModuleNotFoundError: No module named 'psycopg2' #3367

New issue

Closed

opened 2026-03-14 07:13:05 +03:00 by kerem · 0 comments

kerem commented

2026-03-14 07:13:05 +03:00

Owner

Originally created by @FurkanAlev on GitHub (Oct 8, 2025).
Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2305

Hello,

I am trying to install Tactical RMM using Docker with an external PostgreSQL 16 server, but the installation fails.

The tactical-init container gets stuck in a loop with the message: "waiting for postgresql container to be ready...".

After extensive troubleshooting with Gemini Pro, we ran a Python command inside the tactical-init container and found the root cause:
ModuleNotFoundError: No module named 'psycopg2'

This indicates that the required PostgreSQL driver is missing from the Python environment.

Troubleshooting steps taken:

Confirmed network connectivity and credentials with a separate psql container on the same network.
Verified all environment variables in .env and docker-compose.yml.
Tried both latest and 1.2.0 tags for the VERSION variable.
Performed a full cleanup (docker compose down, docker volume rm ...) before each attempt to avoid caching issues.

The problem seems to be with the Docker image build.

Originally created by @FurkanAlev on GitHub (Oct 8, 2025). Original GitHub issue: https://github.com/amidaware/tacticalrmm/issues/2305 Hello, I am trying to install Tactical RMM using Docker with an external PostgreSQL 16 server, but the installation fails. The `tactical-init` container gets stuck in a loop with the message: "waiting for postgresql container to be ready...". After extensive troubleshooting with Gemini Pro, we ran a Python command inside the `tactical-init` container and found the root cause: `ModuleNotFoundError: No module named 'psycopg2'` This indicates that the required PostgreSQL driver is missing from the Python environment. Troubleshooting steps taken: - Confirmed network connectivity and credentials with a separate `psql` container on the same network. - Verified all environment variables in `.env` and `docker-compose.yml`. - Tried both `latest` and `1.2.0` tags for the VERSION variable. - Performed a full cleanup (`docker compose down`, `docker volume rm ...`) before each attempt to avoid caching issues. The problem seems to be with the Docker image build. ![Image](https://github.com/user-attachments/assets/74db3791-ea83-46c9-b5cf-41670d07dba8)