Open ghuls opened 2 years ago
In an HPC environment, there is in general no option to install AppImage.
...Nor is there a need to install AppImages. Just download, mark as executable, and run with --appimage-extract-and-run
if your environment does not provide a working FUSE setup.
@probonopd I didn't know about that argument, but it doesn't work anyway as HPC clusters have glibc versions from a milion years ago:
❯ ./zsync2-51-4e549b6-x86_64.AppImage --appimage-extract-and-run
/tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/AppRun: /usr/lib64/libc.so.6: version `GLIBC_2.22' not found (required by /tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/AppRun)
/tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/AppRun: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.20' not found (required by /tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/AppRun)
/tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/AppRun: /usr/lib64/libstdc++.so.6: version `GLIBCXX_3.4.21' not found (required by /tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/AppRun)
/tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/AppRun: /usr/lib64/libgpg-error.so.0: no version information available (required by /tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/usr/bin/../lib/libgcrypt.so.20)
/tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/AppRun: /usr/lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/usr/bin/../lib/libcrypto.so.1.1)
/tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/AppRun: /usr/lib64/libc.so.6: version `GLIBC_2.27' not found (required by /tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/usr/bin/../lib/libgssapi_krb5.so.2)
/tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/AppRun: /usr/lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/usr/bin/../lib/libgnutls.so.30)
/tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/AppRun: /usr/lib64/libc.so.6: version `GLIBC_2.22' not found (required by /tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/usr/bin/../lib/libgnutls.so.30)
/tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/AppRun: /usr/lib64/libc.so.6: version `GLIBC_2.25' not found (required by /tmp/appimage_extracted_81b6fb70f1742dd32187033f6bf21299/usr/bin/../lib/libcrypt.so.1)
Interesting! Luckily this will soon be a thing of the past with
What would be needed to provide apptainer packages from this repository? I have zero experience with them (in fact, I just heard of these today for the first time).
What would be needed to provide apptainer packages from this repository? I have zero experience with them (in fact, I just heard of these today for the first time).
Nowadays providing a docker container with zsync2 should be enough for endusers to build a apptainer image from it.
Well, I'm willing to merge a PR that implements Docker image building with Docker's build-push-action
. Would you prepare one, please?
It would be nice to have zsync2 as Docker/Podman/apptainer images besides AppImage.
In an HPC environment, there is in general no option to install AppImage.
Singularity/Apptainer (http://apptainer.org/) and Podman (rootless Docker) is for example the only way to run containers on our HPC infrastructure. zsync2 is quite difficult to compile natively on old RedHat versions.
Docker/Podman and SingularityApptainer images are quite easy to make from the Apptainer image.
prepare_zsync2_rootfs.sh:
DockerFile
zsync2.def : Singularity/Apptainer file.
We have files that are over 100G in some cases, so zsync2 would be nice to have to make sure the download is correct (and can be resumed).