The rs3 server binary never reads RS3_ENDPOINT; it is a client-only setting for rs3-cli, which only the old healthcheck used. Switch the rs3 healthcheck to `curl --fail .../readyz` with a start period (matching scripts/run_rs3.sh and CI) and remove the now-dead RS3_ENDPOINT from compose.yml, the demo-server compose, run_rs3.sh, and the test workflow. Verification: - git grep RS3_ENDPOINT -> no matches - docker compose config for compose.yml and tools/demo-server/compose.yml
sigma
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.
Demo Server
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 with the files in this directory.
Visit: https://sigma.tosone.cn, username/password: sigma/Admin@123
Status check here: https://grafana.sigma.tosone.cn/public-dashboards/ebf12be7e7f44b59bfe4096f0f51ab88
Deploy Your Own Demo Server
You can change the .env file and change these lines in compose.yaml with your own domain:
- traefik.http.routers.traefik.rule=Host(`traefik.sigma${HOST_DOMAIN}`)
# ...
- traefik.http.routers.sigma.rule=Host(`sigma${HOST_DOMAIN}`)
# ...
- traefik.http.routers.grafana.rule=Host(`grafana.sigma${HOST_DOMAIN}`)
Commands
# Install docker
make install
# Start or restart all of the docker services
make start
# Stop all of the docker services
make stop
# Show this help
make help