Updates `mc` reference docs for several releases of the MinIO Client. - Adds missing flags to `mc admin trace` - Updates `disk` -> `drive` throughout the docs, but not in all cases. - Adds `--airgap flag` to `mc support profile` and `mc support perf` commands. - Updates the flags for `mc ilm add` command - Adds `mc license unregister` command. Closes #571 Closes #614 Closes #627 Closes #633
7.7 KiB
The following tabs provide examples of installing MinIO onto 64-bit
Linux operating systems using RPM, DEB, or binary. The RPM and DEB
packages automatically install MinIO to the necessary system paths and
create a systemd
service file for running MinIO
automatically. MinIO strongly recommends using RPM or DEB installation
routes.
RPM (RHEL)
Use the following commands to download the latest stable MinIO RPM and install it.
wget |minio-rpm| -O minio.rpm
sudo dnf install minio.rpm
DEB (Debian/Ubuntu)
Use the following commands to download the latest stable MinIO DEB and install it:
wget |minio-deb| -O minio.deb
sudo dpkg -i minio.deb
Binary
Use the following commands to download the latest stable MinIO binary
and install it to the system $PATH
:
wget https://dl.min.io/server/minio/release/linux-amd64/minio
chmod +x minio
sudo mv minio /usr/local/bin/
Run the minio server
command to start the MinIO server.
Specify the path to the volume or folder to use as the storage
directory. The minio
process must have full access (rwx
) to the specified path
and all subfolders:
The following example uses the ~/minio-data
folder:
mkdir ~/minio-data
minio server ~/minio-data --console-address ":9090"
The minio server
process prints its output to the system console, similar to the
following:
API: http://192.0.2.10:9000 http://127.0.0.1:9000
RootUser: minioadmin
RootPass: minioadmin
Console: http://192.0.2.10:9090 http://127.0.0.1:9090
RootUser: minioadmin
RootPass: minioadmin
Command-line: https://min.io/docs/minio/linux/reference/minio-mc.html
$ mc alias set myminio http://192.0.2.10:9000 minioadmin minioadmin
Documentation: https://min.io/docs/minio/linux/index.html
WARNING: Detected default credentials 'minioadmin:minioadmin', we recommend that you change these values with 'MINIO_ROOT_USER' and 'MINIO_ROOT_PASSWORD' environment variables
Open your browser to any of the listed Console
addresses to open the MinIO Console <minio-console>
and log in with
the RootUser
and
RootPass
. You can
use the MinIO Console for performing administration on the MinIO
server.
For applications, use the API
addresses to access the MinIO server and
perform S3 operations.
The following steps are optional but recommended for further securing the MinIO deployment.
The following tabs provide examples of updating MinIO onto 64-bit Linux operating systems using RPM, DEB, or binary:
RPM (RHEL)
Use the following commands to download the latest stable MinIO RPM and update the existing installation.
wget |minio-rpm| -O minio.rpm
sudo dnf update minio.rpm
DEB (Debian/Ubuntu)
Use the following commands to download the latest stable MinIO DEB and upgrade the existing installation:
wget |minio-deb| -O minio.deb
sudo dpkg -i minio.deb
Binary
Use the following commands to download the latest stable MinIO binary and overwrite the existing binary:
wget https://dl.min.io/server/minio/release/linux-amd64/minio
chmod +x minio
sudo mv minio /usr/local/bin/
Replace /usr/local/bin
with the location of the existing
MinIO binary. Run which minio
to identify the path if not
already known.
The .deb
or .rpm
packages install the
following systemd
service file to /etc/systemd/system/minio.service
. For
binary installations, create this file manually on all MinIO hosts:
[Unit]
Description=MinIO
Documentation=https://min.io/docs/minio/linux/index.html
Wants=network-online.target
After=network-online.target
AssertFileIsExecutable=/usr/local/bin/minio
[Service]
WorkingDirectory=/usr/local
User=minio-user
Group=minio-user
ProtectProc=invisible
EnvironmentFile=-/etc/default/minio
ExecStartPre=/bin/bash -c "if [ -z \"${MINIO_VOLUMES}\" ]; then echo \"Variable MINIO_VOLUMES not set in /etc/default/minio\"; exit 1; fi"
ExecStart=/usr/local/bin/minio server $MINIO_OPTS $MINIO_VOLUMES
# Let systemd restart this service always
Restart=always
# Specifies the maximum file descriptor number that can be opened by this process
LimitNOFILE=65536
# Specifies the maximum number of threads this process can create
TasksMax=infinity
# Disable timeout logic and wait until process is stopped
TimeoutStopSec=infinity
SendSIGKILL=no
[Install]
WantedBy=multi-user.target
# Built for ${project.name}-${project.version} (${project.name})
The minio.service
file runs as the
minio-user
User and Group by default. You can create the
user and group using the groupadd
and useradd
commands. The following example creates the user, group, and sets
permissions to access the folder paths intended for use by MinIO. These
commands typically require root (sudo
) permissions.
groupadd -r minio-user
useradd -M -r -g minio-user minio-user
chown minio-user:minio-user /mnt/disk1 /mnt/disk2 /mnt/disk3 /mnt/disk4
The specified drive paths are provided as an example. Change them to match the path to those drives intended for use by MinIO.
Alternatively, change the User
and Group
values to another user and group on the system host with the necessary
access and permissions.
MinIO publishes additional startup script examples on github.com/minio/minio-service <minio-service>
.
sudo systemctl start minio.service
Use the following commands to confirm the service is online and functional:
sudo systemctl status minio.service
journalctl -f -u minio.service
MinIO may log an increased number of non-critical warnings while the server processes connect and synchronize. These warnings are typically transient and should resolve as the deployment comes online.
sudo systemctl restart minio.service
Use the following commands to confirm the service is online and functional:
sudo systemctl status minio.service
journalctl -f -u minio.service
MinIO may log an increased number of non-critical warnings while the server processes connect and synchronize. These warnings are typically transient and should resolve as the deployment comes online.