1
0
mirror of https://github.com/minio/docs.git synced 2025-06-04 08:42:23 +03:00

Adds language about having write permission to use mc admin update (#1346)

Closes #1301

Co-authored-by: Andrea Longo <feorlen@users.noreply.github.com>
This commit is contained in:
Daryl White 2024-10-09 11:04:26 -04:00 committed by GitHub
parent d8fd984346
commit 07a1569e87
No known key found for this signature in database
GPG Key ID: B5690EEEBB952194
2 changed files with 8 additions and 2 deletions

View File

@ -123,7 +123,7 @@ The following command updates a MinIO deployment with the specified :ref:`alias
mc admin update ALIAS
The command may fail if the user which a ``minio`` server process runs as does not have read/write permissions to the path of the binary itself.
The user running the ``mc admin update`` command **must** have ``write`` permissions to the location where the binary installs.
You can specify a URL resolving to a specific MinIO server binary version.
Airgapped or internet-isolated deployments may utilize this feature for updating from an internally-accessible server:

View File

@ -22,7 +22,8 @@ The command also supports using a private mirror server for environments where t
After running the command, a prompt displays to confirm the update.
Type ``y`` and ``[ENTER]`` to confirm and proceed with the update.
You may need to use ``sudo`` if your user does not have write permissions for the path where ``mc`` is installed.
The user **must** have ``write`` permissions for the target location where the binary installs.
.. admonition:: Use ``mc admin`` on MinIO Deployments Only
:class: note
@ -44,6 +45,11 @@ MinIO operations are atomic and strictly consistent and as such the restart proc
MinIO strongly recommends only performing simultaneous upgrade-and-restart procedures.
Do not perform "rolling" (that is, one node at a time) upgrade procedures.
Permissions
~~~~~~~~~~~
The user running the command **must** have ``write`` permissions to the target path where the MinIO Server binary installs.
Examples
--------