Bug 2297667 - squashfs support in charliecloud not working
Summary: squashfs support in charliecloud not working
Keywords:
Status: CLOSED ERRATA
Alias: None
Product: Fedora EPEL
Classification: Fedora
Component: charliecloud
Version: epel9
Hardware: All
OS: All
unspecified
unspecified
Target Milestone: ---
Assignee: jogas
QA Contact: Fedora Extras Quality Assurance
URL:
Whiteboard:
Depends On:
Blocks:
TreeView+ depends on / blocked
 
Reported: 2024-07-13 05:34 UTC by Karsten Kretschmer
Modified: 2024-07-25 00:39 UTC (History)
2 users (show)

Fixed In Version: charliecloud-0.38-1.el9
Clone Of:
Environment:
Last Closed: 2024-07-25 00:39:24 UTC
Type: Bug
Embargoed:


Attachments (Terms of Use)
require squashfuse >= 0.1.105 (954 bytes, patch)
2024-07-13 05:34 UTC, Karsten Kretschmer
no flags Details | Diff

Description Karsten Kretschmer 2024-07-13 05:34:05 UTC
Created attachment 2039507 [details]
require squashfuse >= 0.1.105

Description of problem:

Charliecloud does not support Squashfs.

Version-Release number of selected component (if applicable):

charliecloud-0.36-1.el9.x86_64

How reproducible:

always

Steps to Reproduce:
1. ch-run --feature=squash; echo $?
2. ldd /usr/bin/ch-run

Actual results:

1
        linux-vdso.so.1 (0x00007ffd1232f000)
        libc.so.6 => /lib64/libc.so.6 (0x00007fdc53000000)
        /lib64/ld-linux-x86-64.so.2 (0x00007fdc533e3000)

Expected results:

0
        linux-vdso.so.1 (0x00007ffc8eaf1000)
        libsquashfuse_ll.so.0 => /lib64/libsquashfuse_ll.so.0 (0x00007f5aafb40000)
        libfuse3.so.3 => /lib64/libfuse3.so.3 (0x00007f5aafb00000)
        libc.so.6 => /lib64/libc.so.6 (0x00007f5aaf800000)
        libz.so.1 => /lib64/libz.so.1 (0x00007f5aafae6000)
        liblzma.so.5 => /lib64/liblzma.so.5 (0x00007f5aafaba000)
        liblz4.so.1 => /lib64/liblz4.so.1 (0x00007f5aafa96000)
        libzstd.so.1 => /lib64/libzstd.so.1 (0x00007f5aaf729000)
        /lib64/ld-linux-x86-64.so.2 (0x00007f5aafb7d000)

Additional info:

- Charliecloud’s configure looks for "libsquashfuse_ll" which is only present in squashfuse-libs >= 0.1.105.
- There is a typo in the spec file: --with-libsquashfusei=/usr
  The "i" is there by mistake. This leads to:
    configure: WARNING: unrecognized options: --with-libsquashfusei
- Maybe the whole configure option is not necessary anyway because configure finds the squashfuse library if it is new enough.
- I compiled squashfuse on Rocky Linux 9 using the spec file from the "f40" branch (0.1.105-1) and it works with that one.

Comment 1 jogas 2024-07-15 19:48:14 UTC
Thank you for bringing this to my attention. Fixing it now.

Comment 2 jogas 2024-07-15 22:43:49 UTC
Hmm, it doesn't appear that the squashfuse 0.1.105 and squashfuse-devel 0.1.105 exist for epel9 (see scratch build: https://koji.fedoraproject.org/koji/taskinfo?taskID=120547470). I wonder if Rocky Linux 9 is getting the squashfuse package from a different repo other than epel?

What am I missing?

Comment 3 Karsten Kretschmer 2024-07-16 05:05:43 UTC
Yes, 0.1.105 is not yet in epel9, so I used the spec file from the "f40" branch to build updated packages for squashfuse. I then rebuilt charliecloud against those and then its configure finds the squashfuse library and links against it. So squashfuse in epel9 would also need to be updated to at least 0.1.105.

Comment 4 Fedora Update System 2024-07-16 22:35:27 UTC
FEDORA-EPEL-2024-96795dd807 (charliecloud-0.38-1.el9) has been submitted as an update to Fedora EPEL 9.
https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-96795dd807

Comment 5 Fedora Update System 2024-07-17 01:25:34 UTC
FEDORA-EPEL-2024-96795dd807 has been pushed to the Fedora EPEL 9 testing repository.

You can provide feedback for this update here: https://bodhi.fedoraproject.org/updates/FEDORA-EPEL-2024-96795dd807

See also https://fedoraproject.org/wiki/QA:Updates_Testing for more information on how to test updates.

Comment 6 Fedora Update System 2024-07-25 00:39:24 UTC
FEDORA-EPEL-2024-96795dd807 (charliecloud-0.38-1.el9) has been pushed to the Fedora EPEL 9 stable repository.
If problem still persists, please make note of it in this bug report.


Note You need to log in before you can comment on or make changes to this bug.