Comments (11)
Hi @lukebelbina. We've merged the fixes and released a new Docker image. The reproduction you shared now works for me. I'll close this, but feel free to re-open if you're facing new issues. Thank you for your patience and apologies for the issues. And thank you for reporting!
from paradedb.
@lukebelbina In our latest release, we upgraded our Docker image from postgres
to bitnami/postgresql
. This requires a different docker run
command:
docker run \
--name paradedb \
-e POSTGRESQL_USERNAME=<user> \
-e POSTGRESQL_PASSWORD=<password> \
-e POSTGRESQL_DATABASE=<dbname> \
-e POSTGRESQL_POSTGRES_PASSWORD=<superuser_password> \
-v paradedb_data:/bitnami/postgresql \
-p 5432:5432 \
-d \
paradedb/paradedb:latest
(See the README.md).
Apologies for this breaking change. We won't be making a big Docker image overhaul like this again -- We had to to start supporting more serious enterprise workloads and offer higher security guarantees
from paradedb.
Thanks @philippemnoel for the prompt response.
Unfortunately running
docker run \
--name paradedb \
-e POSTGRESQL_USERNAME=postgres \
-e POSTGRESQL_PASSWORD=1234 \
-e POSTGRESQL_DATABASE=test_db \
-e POSTGRESQL_POSTGRES_PASSWORD=1234 \
-v paradedb_data:/bitnami/postgresql \
-p 5435:5432 \
-d \
paradedb/paradedb:latest
Is behaving the same way.
I tested this on my Arch linux dev machine, my Arch linux laptop, and also on an Ubuntu server and behaved the same in all the environments crashing at Starting PostgreSQL in background...
with no obvious error logs.
from paradedb.
Have you deleted the Docker volume and images? Since they're named the same, it might be cached. You previously ran a docker image without passing -e POSTGRESQL_POSTGRES_PASSWORD
, which is required for the background PostgreSQL to properly initialize and install the ParadeDB extensions. That could explain what you're experiencing
from paradedb.
Is it at all possible for you to stop your local postgres and try with port 5432? Our extensions installation are here: https://github.com/paradedb/paradedb/blob/dev/docker/01_bootstrap.sh and I'm now suspecting the issue might be due to the different port you're using
from paradedb.
Yeah, I did and the Ubuntu machine and my laptop were totally clean first time runs.
I went ahead and created a quick video 45 second video reproducing it:
https://www.loom.com/share/ebb0e871c3364ea8bca48a3cfdccbc63?sid=cae8dc14-a59b-4b35-b8fe-55f3be2c6987
After the video I turned off Postgres and tried it again with no port stuff and same issue. Also on the Ubuntu machine I tried it on Postgres isn't installed. Screenshot below showing nothing on port 5432
I'll go ahead and try it on a clean Ubuntu virtual machine next
from paradedb.
Yeah, I did and the Ubuntu machine and my laptop were totally clean first time runs.
I went ahead and created a quick video 45 second video reproducing it:
https://www.loom.com/share/ebb0e871c3364ea8bca48a3cfdccbc63?sid=cae8dc14-a59b-4b35-b8fe-55f3be2c6987
After the video I turned off Postgres and tried it again with no port stuff and same issue. Also on the Ubuntu machine I tried it on Postgres isn't installed. Screenshot below showing nothing on port 5432
I'll go ahead and try it on a clean Ubuntu virtual machine next
Okay, thank you for making the video. Let me give it a shot on my own and will lyk
from paradedb.
I went ahead and installed Ubuntu 22 server on a virtual machine with a totally clean Docker installation.
I tried to run it without a volume or port and same error:
docker run \
--name paradedb \
-e POSTGRESQL_USERNAME=postgres \
-e POSTGRESQL_PASSWORD=1234 \
-e POSTGRESQL_DATABASE=testdb \
-e POSTGRESQL_POSTGRES_PASSWORD=1234 \
paradedb/paradedb:latest
postgresql 22:17:09.82 INFO ==>
postgresql 22:17:09.85 INFO ==> Welcome to the Bitnami postgresql container
postgresql 22:17:09.87 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers
postgresql 22:17:09.89 INFO ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
postgresql 22:17:09.91 INFO ==>
postgresql 22:17:10.11 INFO ==> ** Starting PostgreSQL setup **
postgresql 22:17:10.25 INFO ==> Validating settings in POSTGRESQL_* env vars..
postgresql 22:17:10.33 INFO ==> Loading custom pre-init scripts...
postgresql 22:17:10.39 INFO ==> Initializing PostgreSQL database...
postgresql 22:17:10.61 INFO ==> pg_hba.conf file not detected. Generating it...
postgresql 22:17:10.63 INFO ==> Generating local authentication configuration
postgresql 22:17:14.83 INFO ==> Starting PostgreSQL in background...
postgresql 22:17:15.55 INFO ==> Changing password of postgres
postgresql 22:17:15.76 INFO ==> Configuring replication parameters
postgresql 22:17:16.16 INFO ==> Configuring synchronous_replication
postgresql 22:17:16.18 INFO ==> Configuring fsync
postgresql 22:17:16.48 INFO ==> Stopping PostgreSQL...
waiting for server to shut down.... done
server stopped
postgresql 22:17:16.75 INFO ==> Loading custom scripts...
postgresql 22:17:16.81 INFO ==> Loading user's custom files from /docker-entrypoint-initdb.d ...
postgresql 22:17:16.83 INFO ==> Starting PostgreSQL in background...
docker container ls -a
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
f1273dec6b34 paradedb/paradedb:latest "/opt/bitnami/script…" 37 seconds ago Exited (1) 28 seconds ago paradedb
from paradedb.
I went ahead and installed Ubuntu 22 server on a virtual machine with a totally clean Docker installation.
I tried to run it without a volume or port and same error:
docker run \ --name paradedb \ -e POSTGRESQL_USERNAME=postgres \ -e POSTGRESQL_PASSWORD=1234 \ -e POSTGRESQL_DATABASE=testdb \ -e POSTGRESQL_POSTGRES_PASSWORD=1234 \ paradedb/paradedb:latest postgresql 22:17:09.82 INFO ==> postgresql 22:17:09.85 INFO ==> Welcome to the Bitnami postgresql container postgresql 22:17:09.87 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers postgresql 22:17:09.89 INFO ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues postgresql 22:17:09.91 INFO ==> postgresql 22:17:10.11 INFO ==> ** Starting PostgreSQL setup ** postgresql 22:17:10.25 INFO ==> Validating settings in POSTGRESQL_* env vars.. postgresql 22:17:10.33 INFO ==> Loading custom pre-init scripts... postgresql 22:17:10.39 INFO ==> Initializing PostgreSQL database... postgresql 22:17:10.61 INFO ==> pg_hba.conf file not detected. Generating it... postgresql 22:17:10.63 INFO ==> Generating local authentication configuration postgresql 22:17:14.83 INFO ==> Starting PostgreSQL in background... postgresql 22:17:15.55 INFO ==> Changing password of postgres postgresql 22:17:15.76 INFO ==> Configuring replication parameters postgresql 22:17:16.16 INFO ==> Configuring synchronous_replication postgresql 22:17:16.18 INFO ==> Configuring fsync postgresql 22:17:16.48 INFO ==> Stopping PostgreSQL... waiting for server to shut down.... done server stopped postgresql 22:17:16.75 INFO ==> Loading custom scripts... postgresql 22:17:16.81 INFO ==> Loading user's custom files from /docker-entrypoint-initdb.d ... postgresql 22:17:16.83 INFO ==> Starting PostgreSQL in background... docker container ls -a CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES f1273dec6b34 paradedb/paradedb:latest "/opt/bitnami/script…" 37 seconds ago Exited (1) 28 seconds ago paradedb
Can you try with a different POSTGRESQL_USERNAME than "postgres"?
from paradedb.
Same again on the clean Ubuntu Virtual Machine.
docker run \
--name paradedb \
-e POSTGRESQL_USERNAME=pguser \
-e POSTGRESQL_PASSWORD='sTro0ng$password' \
-e POSTGRESQL_DATABASE=my_db \
-e POSTGRESQL_POSTGRES_PASSWORD='superSecr$tpass' \
paradedb/paradedb:latest
postgresql 00:33:55.99 INFO ==>
postgresql 00:33:56.02 INFO ==> Welcome to the Bitnami postgresql container
postgresql 00:33:56.04 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers
postgresql 00:33:56.06 INFO ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues
postgresql 00:33:56.08 INFO ==>
postgresql 00:33:56.28 INFO ==> ** Starting PostgreSQL setup **
postgresql 00:33:56.42 INFO ==> Validating settings in POSTGRESQL_* env vars..
postgresql 00:33:56.50 INFO ==> Loading custom pre-init scripts...
postgresql 00:33:56.56 INFO ==> Initializing PostgreSQL database...
postgresql 00:33:56.78 INFO ==> pg_hba.conf file not detected. Generating it...
postgresql 00:33:56.80 INFO ==> Generating local authentication configuration
postgresql 00:34:00.62 INFO ==> Starting PostgreSQL in background...
postgresql 00:34:01.30 INFO ==> Changing password of postgres
postgresql 00:34:01.42 INFO ==> Creating user pguser
postgresql 00:34:01.54 INFO ==> Granting access to "pguser" to the database "my_db"
postgresql 00:34:01.70 INFO ==> Setting ownership for the 'public' schema database "my_db" to "pguser"
postgresql 00:34:01.88 INFO ==> Configuring replication parameters
postgresql 00:34:02.26 INFO ==> Configuring synchronous_replication
postgresql 00:34:02.28 INFO ==> Configuring fsync
postgresql 00:34:02.74 INFO ==> Stopping PostgreSQL...
waiting for server to shut down.... done
server stopped
postgresql 00:34:03.11 INFO ==> Loading custom scripts...
postgresql 00:34:03.17 INFO ==> Loading user's custom files from /docker-entrypoint-initdb.d ...
postgresql 00:34:03.19 INFO ==> Starting PostgreSQL in background...
luke@ubuntu-test-vm:~$
from paradedb.
Same again on the clean Ubuntu Virtual Machine.
docker run \ --name paradedb \ -e POSTGRESQL_USERNAME=pguser \ -e POSTGRESQL_PASSWORD='sTro0ng$password' \ -e POSTGRESQL_DATABASE=my_db \ -e POSTGRESQL_POSTGRES_PASSWORD='superSecr$tpass' \ paradedb/paradedb:latest postgresql 00:33:55.99 INFO ==> postgresql 00:33:56.02 INFO ==> Welcome to the Bitnami postgresql container postgresql 00:33:56.04 INFO ==> Subscribe to project updates by watching https://github.com/bitnami/containers postgresql 00:33:56.06 INFO ==> Submit issues and feature requests at https://github.com/bitnami/containers/issues postgresql 00:33:56.08 INFO ==> postgresql 00:33:56.28 INFO ==> ** Starting PostgreSQL setup ** postgresql 00:33:56.42 INFO ==> Validating settings in POSTGRESQL_* env vars.. postgresql 00:33:56.50 INFO ==> Loading custom pre-init scripts... postgresql 00:33:56.56 INFO ==> Initializing PostgreSQL database... postgresql 00:33:56.78 INFO ==> pg_hba.conf file not detected. Generating it... postgresql 00:33:56.80 INFO ==> Generating local authentication configuration postgresql 00:34:00.62 INFO ==> Starting PostgreSQL in background... postgresql 00:34:01.30 INFO ==> Changing password of postgres postgresql 00:34:01.42 INFO ==> Creating user pguser postgresql 00:34:01.54 INFO ==> Granting access to "pguser" to the database "my_db" postgresql 00:34:01.70 INFO ==> Setting ownership for the 'public' schema database "my_db" to "pguser" postgresql 00:34:01.88 INFO ==> Configuring replication parameters postgresql 00:34:02.26 INFO ==> Configuring synchronous_replication postgresql 00:34:02.28 INFO ==> Configuring fsync postgresql 00:34:02.74 INFO ==> Stopping PostgreSQL... waiting for server to shut down.... done server stopped postgresql 00:34:03.11 INFO ==> Loading custom scripts... postgresql 00:34:03.17 INFO ==> Loading user's custom files from /docker-entrypoint-initdb.d ... postgresql 00:34:03.19 INFO ==> Starting PostgreSQL in background... luke@ubuntu-test-vm:~$
I can reproduce and have identified the cause of the issue. Working on an urgent fix
from paradedb.
Related Issues (20)
- BM25 scoring of specific entry sets for hybrid search HOT 2
- Add support for AGE on the ParadeDB Docker image HOT 4
- Convert `runtests.sh` to GitHub Actions file
- Convert ParadeDB extensions publishing to `dpkg-deb`
- Autocomplete does not work HOT 1
- Date/timestamps are stored incorrectly
- Unexpected behavior with large precision/scales for numerics
- Writer failures causes table to become unqueryable
- Write tests for vacuum
- Support timestamp with time zone
- autocomplete documentation not working in 0.5.8 HOT 1
- Document type support for `pg_analytics`
- Show users a better error message for unsupported timestamp ranges HOT 2
- Show users a better error message for complex updates
- [BUG] Cannot copy data from heap table if there is 'ON CONFLICT DO NOTHING' HOT 1
- Parquet tables don't respect primary keys
- Support timestamp with time zone
- Use deltalake for write ahead HOT 1
- deb cannot be installed on Debian 11 HOT 4
Recommend Projects
-
React
A declarative, efficient, and flexible JavaScript library for building user interfaces.
-
Vue.js
🖖 Vue.js is a progressive, incrementally-adoptable JavaScript framework for building UI on the web.
-
Typescript
TypeScript is a superset of JavaScript that compiles to clean JavaScript output.
-
TensorFlow
An Open Source Machine Learning Framework for Everyone
-
Django
The Web framework for perfectionists with deadlines.
-
Laravel
A PHP framework for web artisans
-
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.
-
Visualization
Some thing interesting about visualization, use data art
-
Game
Some thing interesting about game, make everyone happy.
Recommend Org
-
Facebook
We are working to build community through open source technology. NB: members must have two-factor auth.
-
Microsoft
Open source projects and samples from Microsoft.
-
Google
Google ❤️ Open Source for everyone.
-
Alibaba
Alibaba Open Source for everyone
-
D3
Data-Driven Documents codes.
-
Tencent
China tencent open source team.
from paradedb.