Sigma is an image registry that is extremely easy to deploy and maintain, and it adheres to the interface standards defined by the OCI Distribution Specification 1.1, it can also support any other client programs that follow the interface definition of the OCI Distribution Specification, such as oras, apptainer, helm, and nerdctl.
Now you can use this command to run a simple server:
docker run --name sigma -p 3000:3000 --rm tosone/sigma:nightly-alpineThe default username and password is: sigma/Admin@123. If you want to modify the default password, please refer to the configuration instructions.
It is deployed on an AWS EC2 instance (2C4G, 40G disk) running Debian 12.1 as the Linux distribution. The Docker version used is 25.0.3. The demo server was set up following these instructions.
Visit: https://sigma.tosone.cn, username/password: sigma/Admin@123
The diagram below maps Sigma's main runtime layers, from client entry points to request handling, background workers, and the infrastructure services they depend on.
- Support docker registry v2 protocol.
- Support OCI Image v1 Format and OCI Image Index v1 Format.
- Support OCI artifacts such as helm and so on.
- Support OCI sbom.
- Support Image security scan.
- Support registry proxy.
- Support Namespace quota.
- Support Image automatic garbage collection.
- Support Image sign.
- Support Image build in docker, podman and kubernetes.
- Support Image replication.
Sigma provides two integration paths for AI clients and external automation:
- Embedded MCP server: Sigma can expose registry management tools through the
existing server process. It is disabled by default and can be enabled through
the
mcpconfiguration section. See MCP Server. - External REST API skill:
tools/skill/sigma-api-operatorpackages a reusable skill andswagger.yamlso CLI agents such as Claude Code or Copilot CLI can discover Sigma APIs and operate resources through HTTP requests.