search

apptainer / apptainer-admindocs

Other
2 stars 15 forks source link

Import sylabs admindocs #146

Closed DrDaveD closed 8 months ago

DrDaveD commented 8 months ago

Import the following sylabs admindocs PRs:

Also review these to see if they're better than what we already have:

DrDaveD commented 8 months ago

@afbjorklund Could you please look at sylabs/singularity-admindocs#116 to see if there's any of that you'd like to see imported into apptainer-admindocs?

afbjorklund commented 8 months ago

@DrDaveD : No, there doesn't seem to be anything in that singularity documentation that is not covered by apptainer.

It is possible to remove the Vagrant documentation, and to make the Lima documentation more verbose. But the vagrant is still valid, even if not Open Source and not supporting ARM, and I'm not sure about copying a lot of text from brew and lima because that probably means that it will need to be updated. The basics should stay more the same, over time...

Some differences:

1) Singularity (CE) is using Alma + EPEL, where Apptainer uses Ubuntu LTS + PPA. It was mostly due to the size. Singularity template is not bundled with Lima, so it is downloaded from https: instead of using template:

2) Singularity wrapper is done using shell flags (-B), instead of the more transparent apptainer.lima wrapper It seems to have copied the bug with -H versus -B that apptainer had, which lead to having a read-only home...

Other issues are the same:

1) Where to store the images in the Lima instance, when home directory ($PWD) is read-only Looks like Singularity changed '/tmp/lima' to be read-only too, so have to use limactl cp then.

2) Still using the default qemu and sshfs, instead of new vz and virtiofs (currently "experimental") If you want to compare performance, you can use --vm-type vz --mount-type virtiofs with start.

DrDaveD commented 8 months ago

Thanks for your reply. Ok on not taking any updates for the lima doc. I already decided to remove the Vagrant documentation for macOS, via #150. I don't think there's a good reason to confuse things by documenting two options.

afbjorklund commented 8 months ago

If it is ever needed, it would be possible to add some more hypervisor drivers to Lima - such as the one for VirtualBox... But so far, most of the focus has been to use the new Apple Virtualization.framework* rather than the legacy Oracle one.

* limactl start --vm-type vz --mount-type virtiofs

https://lima-vm.io/docs/config/vmtype/#vz (experimental)

afbjorklund commented 8 months ago

Lima currently uses WSL on Windows*, but it would be possible to use Hyper-V or QEMU (with WHPX) or even VirtualBox. Running in a system container (like in WSL2) makes things rather "different", compared to the regular VM environment.

* limactl start --vm-type=wsl2 --mount-type=wsl2

https://lima-vm.io/docs/config/vmtype/#wsl2 (experimental)