From 07a1569e8724769d0bc952d9ab1773ebc4b3404e Mon Sep 17 00:00:00 2001 From: Daryl White <53910321+djwfyi@users.noreply.github.com> Date: Wed, 9 Oct 2024 11:04:26 -0400 Subject: [PATCH] Adds language about having write permission to use `mc admin update` (#1346) Closes #1301 Co-authored-by: Andrea Longo --- source/includes/linux/steps-upgrade-minio-deployment.rst | 2 +- source/reference/minio-mc-admin/mc-admin-update.rst | 8 +++++++- 2 files changed, 8 insertions(+), 2 deletions(-) diff --git a/source/includes/linux/steps-upgrade-minio-deployment.rst b/source/includes/linux/steps-upgrade-minio-deployment.rst index d8fa02a8..b0126272 100644 --- a/source/includes/linux/steps-upgrade-minio-deployment.rst +++ b/source/includes/linux/steps-upgrade-minio-deployment.rst @@ -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: diff --git a/source/reference/minio-mc-admin/mc-admin-update.rst b/source/reference/minio-mc-admin/mc-admin-update.rst index 9b679b8d..afe94642 100644 --- a/source/reference/minio-mc-admin/mc-admin-update.rst +++ b/source/reference/minio-mc-admin/mc-admin-update.rst @@ -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 --------