Local MinIO storage
The tengri-minio package installs a local S3-compatible MinIO object storage on the same server and configures it for Tengri.
This page describes where the storage credentials come from, how to view and change them, what happens when the package is upgraded or removed, and how to troubleshoot common problems.
Overview
The package installs the minio server, the minio-client tool and the minio.service unit, which serves the S3 API on port 9002 and the web console on port 9001.
The installation creates the prostore bucket (Tengri data) and the mimir bucket (metrics), the prostore policy and the public_loader service account, which can only access the Stage/ and iceberg/public/ paths of the prostore bucket.
Tengri accesses the storage as the built-in MinIO user minioadmin.
The password of this user is generated when the package is installed: a random string of 30–40 Latin letters and digits.
The password never appears in any package file or in the installation output.
Where the credentials are kept
| File | Purpose |
|---|---|
|
The source of the credentials for the Tengri services: |
|
MinIO startup parameters: |
|
Tengri settings overriding |
minio.service starts through a wrapper that assembles the credentials from the two files: a value in /etc/default/tengri-minio takes precedence, what is missing there comes from secrets.env.
The user and the password are looked up independently; when the user is set nowhere, minioadmin is used.
Differences between the files are reported to the journal without revealing the values.
To view the current credentials:
sudo grep '^TNGRI_S3_' /etc/tengri/secrets.env
|
|
Changing the password
-
Set the new values in
/etc/default/tengri-minio(the minimum MinIO password length is 8 characters):MINIO_ROOT_USER=minioadmin MINIO_ROOT_PASSWORD=<new password> -
Copy them to
secrets.envfor the Tengri services:sudo tengri-minio-sync-credentialsThe command only copies the values from
/etc/default/tengri-minioto/etc/tengri/secrets.env; it generates nothing and restarts nothing. Iftengri.confholds different values, it warns about them. -
Restart the services:
sudo systemctl restart minio tengri
The password may stay in /etc/default/tengri-minio afterwards or be removed from it: secrets.env already holds a copy, and the wrapper takes the password from there.
The public_loader account is not affected by a password change.
|
|
Upgrading from previous versions
On upgrade the package checks whether it knows the password of the running server and reports the outcome in the installation output:
-
No password was set before — a new one is generated and written to
secrets.env, and the MinIO and Tengri services are restarted. Nothing needs to be done. -
A password is set in
/etc/default/tengri-minio— it is copied tosecrets.env, nothing is generated. The output showsNOTICE: THE MINIO ROOT CREDENTIALS … WERE COPIED. -
The password is unknown: the server runs with a password that neither file holds — the package is installed, but
minio.servicewill not start. The output showsWARNING: THE MINIO ROOT PASSWORD IS NOT KNOWN TO THE PACKAGES.
In the last case there are two ways forward:
-
If the administrator knows the password — set it in
/etc/default/tengri-minioand follow Changing the password. -
If the stored data is not needed — stop the service, empty the data directory and reinstall the package; the reinstallation generates a new password:
sudo systemctl stop minio sudo rm -rf /var/lib/minio/* sudo apt install --reinstall tengri-minio
Troubleshooting
The wrapper records every reason minio.service refuses to start in the service journal:
sudo journalctl -u minio -n 50
A configuration error exits the service with code 78, and systemd does not restart it automatically: after fixing the files, start the service by hand with sudo systemctl restart minio.
| Journal message | What to do |
|---|---|
|
No file holds a password. Set it in |
|
The variable exists in the named file with an empty value. Set a value or remove the line. |
|
Restore the |
|
The values in the files differ; the service starts. If |
To verify that the Tengri services hold the same credentials as MinIO, run the client as the user from secrets.env:
sudo sh -c '. /etc/tengri/secrets.env; \
MC_HOST_local="http://${TNGRI_S3_ACCESS_KEY_ID:-minioadmin}:${TNGRI_S3_SECRET_ACCESS_KEY}@127.0.0.1:9002" \
minio-client ls local'
The expected output is the list of the mimir and prostore buckets.
Removing the package
|
Removing |
tengri-minio is a dependency of tengri-mimir, which in turn is a dependency of tengri, so apt remove tengri-minio removes those as well.
To switch to an external S3, set TNGRI_S3_ENDPOINT_URL and the credentials in /etc/tengri/tengri.conf without removing the package.