macOS
brew install apptainerlocal Homebrew formula metadata
brew
apptainer のインストール経路、実行ファイル、メタデータ、AI エージェント向けセキュリティノートを確認します。
インストール
brew install apptainerlocal Homebrew formula metadata
sudo apk add apptainerAlpine Linux edge package indexes · apptainer · ソース: dl-cdn.alpinelinux.org
sudo dnf install apptainerFedora Rawhide package metadata · apptainer · ソース: dl.fedoraproject.org
sudo pacman -S apptainerArch Linux sync databases · apptainer · ソース: geo.mirror.pkgbuild.com
sudo zypper install apptaineropenSUSE Tumbleweed package metadata · apptainer · ソース: download.opensuse.org
sudo apt install singularityDebian stable package indexes · singularity · ソース: deb.debian.org
概要
Application container and unprivileged sandbox platform for Linux
履歴
Apptainer is an open-source Linux container platform focused on high-performance computing, reproducibility, security, and unprivileged execution. It is the Linux Foundation continuation and rename of the community Singularity project.
The user guide says Apptainer was first developed at Lawrence Berkeley National Laboratory to run complex applications on HPC clusters in a simple, portable, and reproducible way. It became popular at HPC and academic sites before expanding into industry.
In November 2021, the project announced that Singularity was moving into the Linux Foundation and being renamed Apptainer to avoid confusion with other Singularity-named products and to keep the project under community governance. The announcement says the first Apptainer release would be 1.0 in a new GitHub repository.
The Apptainer changelog records v1.0.0 in March 2022. That release changed the primary executable from `singularity` to `apptainer`, renamed `/etc/singularity` to `/etc/apptainer`, migrated per-user configuration from `~/.singularity` to `~/.apptainer`, and retained a `singularity` command symlink for compatibility.
The v1.1.0 release in September 2022 made a major packaging and security shift: Apptainer no longer installed a setuid-root component by default, relying instead on unprivileged user namespaces for most operations and moving the setuid portion into optional packaging.
Apptainer's adoption is strongest in HPC because it maps container workflows onto shared clusters where Docker's daemon model, root privileges, and isolation defaults are often a poor fit. Its docs emphasize single-file SIF images, integration with GPUs and high-speed filesystems, and preserving the user's host identity by default.
The compatibility strategy helped adoption after the rename. Official docs describe SIF image compatibility, support for `SINGULARITY_` environment variables during transition, a `singularity` symlink to the same binary, and automatic user configuration migration.
Distribution packaging matters because Apptainer is used on managed systems: clusters often install it centrally, admins control global configuration under `/etc/apptainer` or `/usr/local/etc/apptainer`, and users keep remotes, keys, caches, and registry credentials under `~/.apptainer`.
Users build, pull, run, shell into, and exec containers with the `apptainer` CLI. Typical sources include SIF files, Docker/OCI registries, ORAS endpoints, and definition files used to build reproducible scientific or commercial software environments.
Administrators tune `apptainer.conf` for setuid behavior, namespaces, bind mounts, networking, GPUs, cgroups, and helper binary paths. Remote endpoints and keyserver settings are managed through `remote.yaml`; login commands store endpoint credentials, and OCI registry credentials can live in `~/.apptainer/docker-config.json` or a custom `--authfile`.
Apptainer is a packaging story about containers for places where containers are infrastructure, not just developer convenience. It packages runtime policy, SIF image handling, OCI interop, user namespace tradeoffs, cluster admin controls, and backwards compatibility with a large Singularity install base.
For package nerds, the rename is especially interesting because the package intentionally ships compatibility: old command names, old environment variable prefixes, image-format stability, and migration from old user config directories. That reduced the blast radius of a governance and trademark-driven project transition.
セキュリティ状態
infrastructure mutation or orchestration signal.
リスク orange · 信頼度 中 · infrastructure
エージェントに無人実行させる前に、このツールが平文の認証情報を読むか、リモート状態を書き込むか、成果物を公開するか、プラグインを起動するかを確認してください。
local files
These source-backed paths show where this package keeps local settings or durable credentials. Automic Vault can use them as review targets for secret scanning, migration, and command approval.
Config paths the tool may read or write during local use.
/usr/local/etc/apptainer/apptainer.conf/etc/apptainer/apptainer.conf/usr/local/etc/apptainer/remote.yaml/etc/apptainer/remote.yamlCredential-bearing paths to review before unattended agent runs.
~/.apptainer/remote.yaml~/.apptainer/docker-config.json実行可能ファイル
| コマンド | 種類 | 公開範囲 | メモ |
|---|---|---|---|
apptainer | cli | グローバル実行可能ファイル | |
run-singularity | cli | グローバル実行可能ファイル | |
singularity | cli | グローバル実行可能ファイル |
鮮度
これらの信号は、ページ生成時期、パッケージマネージャの活動、上流リリース比較を分けて示します。バージョン遅れは、証拠 URL と比較可能なバージョンがある場合だけ警告されます。
https://github.com/apptainer/apptainer
インストールメタデータ
| パッケージキー | brew:apptainer |
|---|---|
| バージョン | 1.5.2 |
| パッケージマネージャ | Homebrew |
| パッケージマネージャページ | https://formulae.brew.sh/formula/apptainer |
| ホームページ | https://apptainer.org/ |
| リポジトリ | https://github.com/apptainer/apptainer |
| 上流ドキュメント | https://apptainer.org/docs/admin/main |
| ライセンス | BSD-3-Clause |
| ソースアーカイブ | https://github.com/apptainer/apptainer/releases/download/v1.5.2/apptainer-1.5.2.tar.gz |
| 最終更新 | 2026-06-23T23:30:10Z |
| Pulse | updated |
| 依存関係 | libseccomp, squashfs |
| ビルド依存関係 | go, pkgconf |
| Bottle | 利用可能 (対象 arm64_linux, x86_64_linux) |
| Homebrew post-install | 未定義 |
| サービス | 宣言なし |
レジストリ情報
| Source Database | Homebrew formula API |
|---|---|
| Tap | homebrew/core |
| Full Name | apptainer |
| Version Scheme | 0 |
| Revision | 0 |
| Head Version | HEAD |
| Requirements |
|
| Bottle Stable Root URL | https://ghcr.io/v2/homebrew/core |
| Deprecated | no |
| Disabled | no |
| Keg Only | no |
| URL Keys |
|
ソースデータベース一致
一致は外部パッケージマネージャインデックスから取得され、ローカルの Automic Vault パッケージリンクとは分けて表示されます。
apptainer 1.5.1-r0
Application containers for Linux
sudo apk add apptainerapptainer-bash-completion 1.5.1-r0
Bash completions for apptainer
sudo apk add apptainer-bash-completionapptainer-doc 1.5.1-r0
Application containers for Linux (documentation)
sudo apk add apptainer-docapptainer-suid 1.5.1-r0
Application containers for Linux (SUID helper binary)
sudo apk add apptainer-suidapptainer 1.5.0-1.fc45
Application and environment virtualization formerly known as Singularity
sudo dnf install apptainerapptainer-suid 1.5.0-1.fc45
Setuid component of Apptainer
sudo dnf install apptainer-suidapptainer 1.5.1-1
Application containers for secure high performance computing
sudo pacman -S apptainerapptainer 1.4.5-6.1
Application and environment virtualization
sudo zypper install apptainerapptainer-leap 1.4.5-6.1
Apptainer Definition File Templates for current openSUSE Leap
sudo zypper install apptainer-leapsingularity 1.0.0+git20241231-3
game where one becomes the singularity
https://singularity.github.io/
sudo apt install singularitysingularity 1.0.0-1
game where one becomes the singularity
https://singularity.github.io/
sudo apt install singularitysingularity 4.4.2-r0
Application containers focused on reproducibility for scientific computing and HPC world.
https://www.sylabs.io/singularity/
sudo apk add singularitysingularity-bash-completion 4.4.2-r0
Bash completions for singularity
https://www.sylabs.io/singularity/
sudo apk add singularity-bash-completionsingularity-doc 4.4.2-r0
Application containers focused on reproducibility for scientific computing and HPC world. (documentation)
https://www.sylabs.io/singularity/
sudo apk add singularity-docsingularity 1.1-3
Endgame: Singularity - simulation of true AI
http://emhsoft.com/singularity/index.html
sudo pacman -S singularityソース経路
このページは scripts/generate-pkg-sqlite.py が生成した非公開のパッケージ SQLite アーティファクトから av-web によって提供されます。
View the package source record on GitHub.