mirror of
https://github.com/hanzoai/s3.git
synced 2026-11-03 03:07:41 +00:00
zeekay
679a9bed4f
- Replace all MinIO brand references with S3 in docs, helm charts, and comments - Replace quay.io/minio images with ghcr.io/hanzoai/s3 and ghcr.io/hanzos3/* - Replace min.io domains: docs→docs.hanzo.ai, dl→dl.hanzo.space, play→play.hanzo.space - Replace slack.min.io with hanzo.ai/discord - Replace subnet.min.io with subnet.hanzo.ai - Update Makefile REPO to ghcr.io/hanzoai - Update helm values: mc image, OIDC clientId, service account name - Update Go source user-facing URLs and messages - Fix test configs and grafana dashboard descriptions
Deploy S3 on Chrooted Environment 
Chroot allows user based namespace isolation on many standard Linux deployments.
1. Prerequisites
- Familiarity with chroot
- Chroot installed on your machine.
2. Install S3 in Chroot
Note: S3 community edition is now distributed as source code only. Pre-compiled binaries are no longer provided for new releases.
Build S3 from source and install it in the chroot directory:
# Build S3 from source
go install github.com/hanzoai/s3@latest
# Create the bin directory in your chroot
mkdir -p /mnt/export/${USER}/bin
# Copy the built binary to the chroot directory
cp $(go env GOPATH)/bin/minio /mnt/export/${USER}/bin/minio
chmod +x /mnt/export/${USER}/bin/minio
Alternatively, if you have an existing legacy binary, you can still use it, but note that it will not receive updates.
Bind your proc mount to the target chroot directory
sudo mount --bind /proc /mnt/export/${USER}/proc
3. Run Standalone S3 in Chroot
GNU/Linux
sudo chroot --userspec username:group /mnt/export/${USER} /bin/minio --config-dir=/.minio server /data
Endpoint: http://192.168.1.92:9000 http://65.19.167.92:9000
AccessKey: MVPSPBW4NP2CMV1W3TXD
SecretKey: X3RKxEeFOI8InuNWoPsbG+XEVoaJVCqbvxe+PTOa
...
...
Instance is now accessible on the host at port 9000, proceed to access the Web browser at http://127.0.0.1:9000/