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

Qt5 error in containerized version of QGIS #46841

Closed
1 of 2 tasks
lgorenstein opened this issue Jan 14, 2022 · 4 comments
Closed
1 of 2 tasks

Qt5 error in containerized version of QGIS #46841

lgorenstein opened this issue Jan 14, 2022 · 4 comments
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.

Comments

@lgorenstein
Copy link

What is the bug or the crash?

I am trying to run containerized version of QGIS on a high-performance computing cluster. Docker is not supported on the cluster (due to elevated privileges), but Singularity containers are embraced - so I am using Singularity's built-in feature to pull down QGIS container from DockerHub and convert it to Singularity format.

Conversion goes without a hitch, but execution throws a weird Qt5 error:

$ singularity pull qgis-3.16.sif docker:https://qgis/qgis:release-3_16     # generates qgis-3.16.sif
$ singularity exec qgis-3.16.sif qgis
/usr/bin/qgis: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory

Which is clearly not true:

$ singularity exec qgis-3.16.sif find /usr -name 'libQt5Core.so.5*' -ls
   122133      0 lrwxrwxrwx   1 root     root           20 Jan  5 13:54 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5 -> libQt5Core.so.5.12.8
   122134      0 lrwxrwxrwx   1 root     root           20 Jan  5 13:54 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12 -> libQt5Core.so.5.12.8
   122135   5391 -rw-r--r--   1 root     root      5519624 Jan  5 13:54 /usr/lib/x86_64-linux-gnu/libQt5Core.so.5.12.8

(note that these are inside of the container, just as they should).

It appears that this very error when running Qt5 applications in some kind of virtualized environment (Docker, Virtualbox, WSL1) is a fairly known thing. E.g.:

For all of them, the (very bizarre, but working) solution seems to add one extra command to the Dockerfile:

strip --remove-section=.note.ABI-tag /usr/lib/x86_64-linux-gnu/libQt5Core.so.5

and the problem disappears.

I was wondering if you'd be willing to add such a line to the QGIS container script.

Steps to reproduce the issue

(assuming you have Singularity installed)

$ singularity pull qgis-3.16.sif docker:https://qgis/qgis:release-3_16
$ singularity exec qgis-3.16.sif qgis
/usr/bin/qgis: error while loading shared libraries: libQt5Core.so.5: cannot open shared object file: No such file or directory

Observed the same for 3.22 as well.

Versions

3.16 and 3.22 (per Docker tags)

Supported QGIS version

  • I'm running a supported QGIS version according to the roadmap.

New profile

  • I tried with a new QGIS profile

Additional context

No response

@lgorenstein lgorenstein added the Bug Either a bug report, or a bug fix. Let's hope for the latter! label Jan 14, 2022
@gioman
Copy link
Contributor

gioman commented Jan 15, 2022

I was wondering if you'd be willing to add such a line to the QGIS container script.

@lgorenstein you can submit a Pull Request and have it reviewed by QGIS core devs.

@gioman gioman added the Feedback Waiting on the submitter for answers label Jan 15, 2022
lgorenstein added a commit to lgorenstein/QGIS that referenced this issue Jan 18, 2022
@lgorenstein
Copy link
Author

@gioman I do not have a suitable Docker infrastructure to test - but happy to make a PR.

@github-actions
Copy link

github-actions bot commented Feb 1, 2022

The QGIS project highly values your report and would love to see it addressed. However, this issue has been left in feedback mode for the last 14 days and is being automatically marked as "stale".
If you would like to continue with this issue, please provide any missing information or answer any open questions. If you could resolve the issue yourself meanwhile, please leave a note for future readers with the same problem and close the issue.
In case you should have any uncertainty, please leave a comment and we will be happy to help you proceed with this issue.
If there is no further activity on this issue, it will be closed in a week.

@github-actions github-actions bot added the stale Uh oh! Seems this work is abandoned, and the PR is about to close. label Feb 1, 2022
@github-actions
Copy link

github-actions bot commented Mar 1, 2022

While we hate to see this happen, this issue has been automatically closed because it has not had any activity in the last 42 days despite being marked as feedback. If this issue should be reconsidered, please follow the guidelines in the previous comment and reopen this issue.
Or, if you have any further questions, there are also further support channels that can help you.

@github-actions github-actions bot closed this as completed Mar 1, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
Bug Either a bug report, or a bug fix. Let's hope for the latter! Feedback Waiting on the submitter for answers stale Uh oh! Seems this work is abandoned, and the PR is about to close.
Projects
None yet
Development

Successfully merging a pull request may close this issue.

2 participants