Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

postgres:14 as quarkus devservice fails to run on M2 macbook #44150

Closed
maxandersen opened this issue Oct 29, 2024 · 3 comments · Fixed by #44191
Closed

postgres:14 as quarkus devservice fails to run on M2 macbook #44150

maxandersen opened this issue Oct 29, 2024 · 3 comments · Fixed by #44191
Labels
kind/bug Something isn't working
Milestone

Comments

@maxandersen
Copy link
Member

Describe the bug

not sure when it started but recently postgres:14 stopped working for me.

error showing it is not multiarch:
The architecture 'amd64' for image 'docker.io/postgres:14' (ID sha256:d4a3e64ed8edfd59f3b853e3fe43e3d549b69f3a08e78841b268cdcf4998313d) does not match the Docker server architecture 'arm64'. This will cause the container to execute much more slowly due to emulation and may lead to timeout failures.

and then the logs showing it simply fails to start:

The files belonging to this database system will be owned by user "postgres".
This user must also own the server process.

The database cluster will be initialized with locale "en_US.utf8".
The default database encoding has accordingly been set to "UTF8".
The default text search configuration will be set to "english".

Data page checksums are disabled.

fixing permissions on existing directory /var/lib/postgresql/data ... ok
creating subdirectories ... ok
selecting dynamic shared memory implementation ... posix
selecting default max_connections ... 100
selecting default shared_buffers ... 128MB
selecting default time zone ... Etc/UTC
creating configuration files ... ok
running bootstrap script ... ok
performing post-bootstrap initialization ... ok
syncing data to disk ... ok

initdb: warning: enabling "trust" authentication for local connections
You can change this by editing pg_hba.conf or using the option -A, or
--auth-local and --auth-host, the next time you run initdb.

Success. You can now start the database server using:

    /usr/lib/postgresql/14/bin/pg_ctl -D /var/lib/postgresql/data -l logfile start

waiting for server to start....2024-10-29 05:36:05.193 UTC [118] LOG:  starting PostgreSQL 14.13 (Debian 14.13-1.pgdg120+1) on x86_64-pc-linux-gnu, compiled by gcc (Debian 12.2.0-14) 12.2.0, 64-bit
2024-10-29 05:36:05.195 UTC [118] LOG:  listening on Unix socket "/var/run/postgresql/.s.PGSQL.5432"
2024-10-29 05:36:05.214 UTC [122] LOG:  database system was shut down at 2024-10-29 05:36:04 UTC
 stopped waiting
pg_ctl: could not start server
Examine the log output.

using postgres only works - which (I assume) means postgres:17 would be a better choice.

Not sure if there is a reason we are on a old version (postgres:14 is from 2021).

Expected behavior

No response

Actual behavior

No response

How to Reproduce?

No response

Output of uname -a or ver

No response

Output of java -version

No response

Quarkus version or git rev

No response

Build tool (ie. output of mvnw --version or gradlew --version)

No response

Additional information

No response

@maxandersen
Copy link
Member Author

if this fixes it we should consider backporting to 3.15

@geoand
Copy link
Contributor

geoand commented Nov 7, 2024

I assume this was fixed by #44191?

@gsmet
Copy link
Member

gsmet commented Nov 16, 2024

Yes, closing.

@gsmet gsmet closed this as completed Nov 16, 2024
@gsmet gsmet added this to the 3.16.2 milestone Nov 16, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
kind/bug Something isn't working
Projects
None yet
3 participants