In Postgres 12.15 Image, LLVMBuildGEP symbol not found.
#1076
Comments
|
I'm experiencing a similar issue with the https://github.com/postgis/docker-postgis - alpine3.18 test. (I'm just guessing)
At least in Alpine3.18, postgresql12 built with EDIT:
|
|
We have the same issue with PostgreSQL 15. We are using the |
|
This is also affecting the |
|
I have the same issue with PostgreSQL 14. I are using the |
|
I understand that upgrading to alpine 3.18 or newer is vital. Because it mitigates the vulnerabilities. @tianon, do you have any thought about this issue? |
|
I also have the same issue with Postgres 13-alpine3.18. 👍 |
|
I wonder, would it be enough to replace postgres/Dockerfile-alpine.template Line 49 in a23c0e9 With llvm15-dev clang15
|
Util docker-library/postgres#1076 is fixed.
|
I'm working on a PR for a fix and should have something up shortly. I'm also trying to work out a test so that we can verify the fix as well. |
|
I have a simple test up in docker-library/official-images#14646 that should help prevent this in the future. Once I can get that merged, I'll open the PR for my branch with the fix (infosiftr@9768eb1) so that the tests will run on the fix PR. |
are you sure? postgres 15.3 supports llvm16 when built against and at runtime fine, since it was ported to LLVMBuildGEP2, afaik (edit: disregard, i'm wrong) |
|
I also had this issue with |
Thank you! comment: As I understand that for the downstream ( ~ Postgis ) build script ( https://github.com/postgis/docker-postgis/blob/b50183f2244f42904d95d2bac3a12d1f16b4e59a/Dockerfile.alpine.template#L85 I don't know what the recommended method for determining the linked LLVM version is, but if there is a recommendation,
|
I hadn't considered that postgis and other extensions would need to install the same llvm-dev/clang versions. 🤔 I think an |
|
Would a package list in the env var work to lower duplication that extensions would have to do? Like we have for |
This reverts commit 2754504. <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> Resolved in docker-library/postgres#1076 ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch ~~- [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file~~ ~~- [ ] I have updated the documentation accordingly~~ ~~- [ ] I have added tests to cover my changes~~ ~~- [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ ~~- [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com>
This reverts commit 2754504. <!-- Raise an issue to propose your change (https://github.com/opencv/cvat/issues). It helps to avoid duplication of efforts from multiple independent contributors. Discuss your ideas with maintainers to be sure that changes will be approved and merged. Read the [Contribution guide](https://opencv.github.io/cvat/docs/contributing/). --> <!-- Provide a general summary of your changes in the Title above --> ### Motivation and context <!-- Why is this change required? What problem does it solve? If it fixes an open issue, please link to the issue here. Describe your changes in detail, add screenshots. --> Resolved in docker-library/postgres#1076 ### How has this been tested? <!-- Please describe in detail how you tested your changes. Include details of your testing environment, and the tests you ran to see how your change affects other areas of the code, etc. --> ### Checklist <!-- Go over all the following points, and put an `x` in all the boxes that apply. If an item isn't applicable for some reason, then ~~explicitly strikethrough~~ the whole line. If you don't do that, GitHub will show incorrect progress for the pull request. If you're unsure about any of these, don't hesitate to ask. We're here to help! --> - [x] I submit my changes into the `develop` branch ~~- [ ] I have added a description of my changes into the [CHANGELOG](https://github.com/opencv/cvat/blob/develop/CHANGELOG.md) file~~ ~~- [ ] I have updated the documentation accordingly~~ ~~- [ ] I have added tests to cover my changes~~ ~~- [ ] I have linked related issues (see [GitHub docs]( https://help.github.com/en/github/managing-your-work-on-github/linking-a-pull-request-to-an-issue#linking-a-pull-request-to-an-issue-using-a-keyword))~~ ~~- [ ] I have increased versions of npm packages if it is necessary ([cvat-canvas](https://github.com/opencv/cvat/tree/develop/cvat-canvas#versioning), [cvat-core](https://github.com/opencv/cvat/tree/develop/cvat-core#versioning), [cvat-data](https://github.com/opencv/cvat/tree/develop/cvat-data#versioning) and [cvat-ui](https://github.com/opencv/cvat/tree/develop/cvat-ui#versioning))~~ ### License - [x] I submit _my code changes_ under the same [MIT License]( https://github.com/opencv/cvat/blob/develop/LICENSE) that covers the project. Feel free to contact the maintainers if that's a concern. Co-authored-by: Maxim Zhiltsov <zhiltsov.max35@gmail.com>
Hello! I am using the Postgres 12 image and Django for my backend application.
However, after updating the Postgres 12 image to version 12.15, I encountered some failed operations due to the absence of
LLVMBuildGEP.The error message is as follows:
Upon investigation, I discovered that the Alpine Linux version in the updated Postgres 12.15 image is now 3.18, and this version no longer includes LLVMBuildGEP because it was removed in LLVM 16. (LLVM 16 Release Notes)
I was able to resolve this issue by reverting my Postgres image version back to 12.14.
The text was updated successfully, but these errors were encountered: