-
Notifications
You must be signed in to change notification settings - Fork 15
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
[Feature Request]Upgrade singularity in bargeOS.img from 2.6.0 to 3.7.2 #108
Comments
Thank you so much for stopping by and sorry for this late reply. I am still thinking how I can restart the Barge project in the near future. Meanwhile, you may be able to build it by yourself with https://github.com/ailispaw/singularity-barge/tree/v3.0 . |
Thanks, I'll give a try. |
I've tried the Vagrantfile, it's very convenient, it seems successfully boot the bargeOS virtualbox image and built the singularity 3.9.9 in it:
but when I run "vagrant ssh" and "singularity -h", the error shows: I've tried "pkg install libseccomp", the error is still there. |
Can you try it with a new box there? To try the box,
|
Barge v2.13.0 has libseccomp v2.4.0 |
It seems that seccomp_notify_respond was added in libseccomp v2.5.0. |
Tested it, the barge v3.0.0-dev works:
|
version 3.2.1 ? |
My fault, I need "vagrant box remove ailispaw/barge" first:
To modify Vagrantfile:
Then "vagrant up", and "vagrant ssh":
Everything is ok now. |
I see, but I don't think that you need to remove the box |
Yesterday, I found Singularity(https://sylabs.io/guides/3.7/user-guide/quick_start.html#install),
It's awesome, I think it's far easier to use than docker.(especially its sanbox feature, it's very convenient for finding package changes)
And what surprised me even more is that bargeOS has integrated Singularity many years ago.(pkg install singularity)
But the version is too old(2.6.0), do you have time to upgrade the Singularity?
The text was updated successfully, but these errors were encountered: