You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Describe the bug
Whenever PostgresContainer is ran using tensorchord/pgvecto-rs:pg16-v0.3.0, it waits forever for postgres to be ready. This happens because pgvecto.rs added -c logging_collector=on to their Dockerfile CMD. This puts all logs after "PostgreSQL init process complete; ready for start up." to a separate file instead of to stdout, which is what PostgresContainer is expecting:
Describe the bug
Whenever PostgresContainer is ran using
tensorchord/pgvecto-rs:pg16-v0.3.0
, it waits forever for postgres to be ready. This happens because pgvecto.rs added-c logging_collector=on
to their Dockerfile CMD. This puts all logs after "PostgreSQL init process complete; ready for start up." to a separate file instead of to stdout, which is what PostgresContainer is expecting:testcontainers-python/modules/postgres/testcontainers/postgres/__init__.py
Lines 117 to 124 in 8f1165d
To Reproduce
https://github.com/theS1LV3R/testcontainers-pgvecto-rs-test
Runtime environment
The text was updated successfully, but these errors were encountered: