-
Notifications
You must be signed in to change notification settings - Fork 25
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
Provide Docker/Podman/apptainer images. #68
Comments
...Nor is there a need to install AppImages. Just download, mark as executable, and run with |
@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:
|
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). |
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 |
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).
The text was updated successfully, but these errors were encountered: