@czk If you add lilac, which is a bot for creating pkg automatically, as co-maintainer, then she will update AUR and create pkg in CN repo upon singularity upgrade.
Search Criteria
Package Details: singularity-container 3.7.1-1
| Git Clone URL: | https://aur.archlinux.org/singularity-container.git (read-only, click to copy) |
|---|---|
| Package Base: | singularity-container |
| Description: | Container platform focused on supporting "Mobility of Compute". |
| Upstream URL: | https://www.sylabs.io/singularity/ |
| Licenses: | |
| Submitter: | czk |
| Maintainer: | czk |
| Last Packager: | czk |
| Votes: | 21 |
| Popularity: | 2.21 |
| First Submitted: | 2016-08-22 20:22 |
| Last Updated: | 2021-02-25 12:33 |
Dependencies (4)
- libseccomp (libseccomp-git)
- squashfs-tools (squashfs-tools-git)
- dep (dep-git, dep-bin) (make)
- go (go-tip, go-git, go-go2go-git, gcc-go-git, gcc-go) (make)
Required by (2)
- python-spython (optional)
- python-sregistry (optional)
Sources (1)
hottea commented on 2020-11-12 03:02
czk commented on 2020-11-11 11:02
@hottea
That's cool. How about an MR to https://github.com/czka/AUR-singularity-container? Once merged, your changes will be automatically commited to this AUR package as well.
hottea commented on 2020-11-10 14:55
Hello, I create a PKGBUILD based on yours. Thanks for your efforts. However,
1. /usr/libexec is not used in ArchLinux, use /usr/lib instead.
2. cryptsetup is missing in deps.
3. BSD license is not included in pkg licenses, so we should add license file to the pkg tarball too.
If you like, you could now install this pkg from Arch Linux Chinese Community Repository.
czk commented on 2020-03-22 13:12
@chwtu
the version printout is correct when building from source
But this PKGBUILD does build from source. Could you elaborate?
chwtu commented on 2020-03-04 16:20
No, since I did not think they would mind it because the version printout is correct when building from source. But nvm as long as everything else works...
czk commented on 2020-03-02 19:06
@chwtu
Why does singularity version of this install show bf6bdb5 instead of the expected version number
Good question. Have you tried asking the authors?
chwtu commented on 2020-02-24 21:59
I previuosly build Singularity from sources of their github and switched to this for convenience and clean removal of old builds.
Possibly a newbie question:
Why does singularity version of this install show bf6bdb5 instead of the expected version number (currently 3.5.2)? This is not even the hash of the commit with this release tag.
czk commented on 2019-01-10 06:11
@gdolle
That's been already fixed with 3.0.2-2.
gdolle commented on 2019-01-09 18:09
Hi @czk
From the admin doc "Singularity must be installed as root for full functionality." [1,2]
Also for security purpose, you prefer to execute singularity containers as regular user by default with limited privileges
(PS. user privilege in a singularity container are the same than on the host).
[1] https://www.sylabs.io/guides/3.0/admin-guide/admin_quickstart.html#build- from-source
[2] https://singularity.lbl.gov/docs-security#can-i-install-singularity-as-a-user
czk commented on 2019-01-09 17:47
You can submit patches to this PKGBUILD via GitHub PRs if you like: https://github.com/czka/AUR-singularity-container
Git config to keep both repos in sync easily:
$ git remote -v
origin git@github.com:czka/AUR-singularity-container.git (fetch)
origin git@github.com:czka/AUR-singularity-container.git (push)
origin ssh+git://aur@aur.archlinux.org/singularity-container.git (push)
Pinned Comments
czk commented on 2019-01-09 17:47
You can submit patches to this PKGBUILD via GitHub PRs if you like: https://github.com/czka/AUR-singularity-container
Git config to keep both repos in sync easily: