From 43932e604a01282ceba9fa215f0efaa3eee1b61b Mon Sep 17 00:00:00 2001 From: abraunegg Date: Thu, 7 Oct 2021 08:13:00 +1100 Subject: [PATCH] Update Docker.md * Reorder sections of document for better readability --- docs/Docker.md | 7 ++++--- 1 file changed, 4 insertions(+), 3 deletions(-) diff --git a/docs/Docker.md b/docs/Docker.md index c060864e..dad3bd27 100644 --- a/docs/Docker.md +++ b/docs/Docker.md @@ -65,17 +65,18 @@ docker run -it --name onedrive -v onedrive_conf:/onedrive/conf \ -e "ONEDRIVE_GID:${ONEDRIVE_GID}" \ driveone/onedrive:latest ``` -**NOTE:** It is also highly advisable for you to replace `${ONEDRIVE_UID}` and `${ONEDRIVE_GID}` with your actual UID and GID as specified by your `id` command output to avoid any any potential user or group conflicts. - **Important:** The 'target' folder of `ONEDRIVE_DATA_DIR` must exist before running the Docker container, otherwise, Docker will create the target folder, and the folder will be given 'root' permissions, which then causes the Docker container to fail upon startup with the following error message: ```bash ROOT level privileges prohibited! ``` +**NOTE:** It is also highly advisable for you to replace `${ONEDRIVE_UID}` and `${ONEDRIVE_GID}` with your actual UID and GID as specified by your `id` command output to avoid any any potential user or group conflicts. **Example:** -``` +```bash export ONEDRIVE_UID=`id -u` export ONEDRIVE_GID=`id -g` +export ONEDRIVE_DATA_DIR="${HOME}/OneDrive" +mkdir -p ${ONEDRIVE_DATA_DIR} docker run -it --name onedrive -v onedrive_conf:/onedrive/conf -v "${ONEDRIVE_DATA_DIR}:/onedrive/data" \ -e "ONEDRIVE_UID:${ONEDRIVE_UID}" \ -e "ONEDRIVE_GID:${ONEDRIVE_GID}" \