Skip to content

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

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

PostgreSQL 14.11 is not able to identify the postmaster daemon. #1208

Closed
vigneshkumar2016 opened this issue Mar 6, 2024 · 3 comments
Closed

Comments

@vigneshkumar2016
Copy link

PostgreSQL 14.11 runs out on error.
Image: Official Image
Version: 14.11
OS: Debian
OS version: bullseye
Container: yes

PostgreSQL errors out on 14.11
Segmentation fault (core dumped). this is quite strange.

PostgreSQL 14.5, 14.6, 14.0 works just fine.

Seems like the compiler is overshooting on the address space to load postgres.

any help here is much appreciated.

@ImreSamu
Copy link
Contributor

ImreSamu commented Mar 6, 2024

Hi @vigneshkumar2016 ,

It's possible that the issue you're encountering is related to libseccomp.
If that's the case, you might consider updating both libseccomp and docker on the host that's running the containers.
( or just use postgres:14.11-bullseye )

For detailed information, including the root cause and potential workarounds, please visit:
#1100 (comment)

@vigneshkumar2016
Copy link
Author

libseccomp

Thanks, this works for me. However the traceback results and coredump looks similar with that of the one which is working and failing. pretty strange to debug. But clearly getting libraries are not getting loaded to the container memory.

@tianon
Copy link
Member

tianon commented Mar 6, 2024

Yeah, the seccomp blocks happen at the kernel level, so strace is one of the few tools that shows what's happening and even then it's usually an obscure EPERM in places it shouldn't be and no real indicator that it's actually seccomp blocking it. 😭

@docker-library docker-library locked and limited conversation to collaborators Mar 6, 2024
@tianon tianon converted this issue into discussion #1209 Mar 6, 2024

This issue was moved to a discussion.

You can continue the conversation there. Go to discussion →

Labels
None yet
Projects
None yet
Development

No branches or pull requests

3 participants