Backport v2.5.x documentation changes

* Backport v2.5.x documentation changes for Docker and Podman
Update ubuntu-package-install.md
2024-05-27 02:52:18 +02:00 · 2023-11-16 09:15:30 +11:00 · 2023-11-10 04:50:50 +11:00 · 2023-09-25 08:04:29 +10:00 · 2023-09-14 07:06:56 +10:00 · 2023-09-11 10:16:50 +10:00
12 changed files with 618 additions and 206 deletions
--- a/contrib/docker/entrypoint.sh
+++ b/contrib/docker/entrypoint.sh
@ -69,6 +69,13 @@ if [ "${ONEDRIVE_UPLOADONLY:=0}" == "1" ]; then
   ARGS=(--upload-only ${ARGS[@]})
 fi

+# Tell client to sync in no-remote-delete mode based on environment variable
+if [ "${ONEDRIVE_NOREMOTEDELETE:=0}" == "1" ]; then
+   echo "# We are synchronizing in no-remote-delete mode"
+   echo "# Adding --no-remote-delete"
+   ARGS=(--no-remote-delete ${ARGS[@]})
+fi
+
 # Tell client to logout based on environment variable
 if [ "${ONEDRIVE_LOGOUT:=0}" == "1" ]; then
   echo "# We are logging out"
--- a/docs/Docker.md
+++ b/docs/Docker.md
@ -15,8 +15,7 @@ This client can be run as a Docker container, with 3 available container base op
 These containers offer a simple monitoring-mode service for the OneDrive Client for Linux.

 The instructions below have been validated on:
-*   Red Hat Enterprise Linux 8.x 
-*   Ubuntu Server 22.04
+*   Fedora 38

 The instructions below will utilise the 'edge' tag, however this can be substituted for any of the other docker tags such as 'latest' from the table above if desired.

@ -24,69 +23,131 @@ The 'edge' Docker Container will align closer to all documentation and features,

 Additionally there are specific version release tags for each release. Refer to https://hub.docker.com/r/driveone/onedrive/tags for any other Docker tags you may be interested in.

-## Basic Setup
-### 0. Install docker using your distribution platform's instructions
-1.  Ensure that SELinux has been disabled on your system. A reboot may be required to ensure that this is correctly disabled.
-2.  Install Docker as per required for your platform. Refer to https://docs.docker.com/engine/install/ for assistance.
-3.  Obtain your normal, non-root user UID and GID by using the `id` command
-4.  As your normal, non-root user, ensure that you can run `docker run hello-world` *without* using `sudo`
+**Note:** The below instructions for docker has been tested and validated when logging into the system as an unprivileged user (non 'root' user).

-Once the above 4 steps are complete and you can successfully run `docker run hello-world` without sudo, only then proceed to 'Pulling and Running the Docker Image'
+## High Level Configuration Steps
+1. Install 'docker' as per your distribution platform's instructions if not already installed.
+2. Configure 'docker' to allow non-privileged users to run Docker commands
+3. Disable 'SELinux' as per your distribution platform's instructions
+4. Test 'docker' by running a test container without using `sudo`
+5. Prepare the required docker volumes to store the configuration and data
+6. Run the 'onedrive' container and perform authorisation
+7. Running the 'onedrive' container under 'docker'

-## Pulling and Running the Docker Image
-### 1. Pull the image
-```bash
-docker pull driveone/onedrive:edge
+## Configuration Steps
+
+### 1. Install 'docker' on your platform
+Install 'docker' as per your distribution platform's instructions if not already installed.
+
+### 2. Configure 'docker' to allow non-privileged users to run Docker commands
+Read https://docs.docker.com/engine/install/linux-postinstall/ to configure the 'docker' user group with your user account to allow your non 'root' user to run 'docker' commands.
+
+### 3. Disable SELinux on your platform
+In order to run the Docker container, SELinux must be disabled. Without doing this, when the application is authenticated in the steps below, the following error will be presented:
+```text
+ERROR: The local file system returned an error with the following message:
+  Error Message:    /onedrive/conf/refresh_token: Permission denied
+
+The database cannot be opened. Please check the permissions of ~/.config/onedrive/items.sqlite3
+```
+The only known work-around for the above problem at present is to disable SELinux. Please refer to your distribution platform's instructions on how to perform this step.
+
+* Fedora: https://docs.fedoraproject.org/en-US/quick-docs/selinux-changing-states-and-modes/#_disabling_selinux
+* Red Hat Enterprise Linux: https://access.redhat.com/solutions/3176
+
+Post disabling SELinux and reboot your system, confirm that `getenforce` returns `Disabled`:
+```text
+$ getenforce
+Disabled
 ```

-**NOTE:** SELinux context needs to be configured or disabled for Docker to be able to write to OneDrive host directory.
+If you are still experiencing permission issues despite disabling SELinux, please read https://www.redhat.com/sysadmin/container-permission-denied-errors

-### 2. Prepare config volume
-The Docker container requries 2 Docker volumes:
+### 4. Test 'docker' on your platform
+Ensure that 'docker' is running as a system service, and is enabled to be activated on system reboot:
+```bash
+sudo systemctl enable --now docker
+```
+
+Test that 'docker' is operational for your 'non-root' user, as per below:
+```bash
+[alex@fedora-38-docker-host ~]$ docker run hello-world
+Unable to find image 'hello-world:latest' locally
+latest: Pulling from library/hello-world
+719385e32844: Pull complete 
+Digest: sha256:88ec0acaa3ec199d3b7eaf73588f4518c25f9d34f58ce9a0df68429c5af48e8d
+Status: Downloaded newer image for hello-world:latest
+
+Hello from Docker!
+This message shows that your installation appears to be working correctly.
+
+To generate this message, Docker took the following steps:
+ 1. The Docker client contacted the Docker daemon.
+ 2. The Docker daemon pulled the "hello-world" image from the Docker Hub.
+    (amd64)
+ 3. The Docker daemon created a new container from that image which runs the
+    executable that produces the output you are currently reading.
+ 4. The Docker daemon streamed that output to the Docker client, which sent it
+    to your terminal.
+
+To try something more ambitious, you can run an Ubuntu container with:
+ $ docker run -it ubuntu bash
+
+Share images, automate workflows, and more with a free Docker ID:
+ https://hub.docker.com/
+
+For more examples and ideas, visit:
+ https://docs.docker.com/get-started/
+
+[alex@fedora-38-docker-host ~]$ 
+```
+
+### 5. Configure the required docker volumes
+The 'onedrive' Docker container requires 2 docker volumes to operate:
 *    Config Volume
 *    Data Volume

-Create the config volume with the following command:
+The first volume is the configuration volume that stores all the applicable application configuration + current runtime state. In a non-containerised environment, this normally resides in `~/.config/onedrive` - in a containerised environment this is stored in the volume tagged as `/onedrive/conf`
+
+The second volume is the data volume, where all your data from Microsoft OneDrive is stored locally. This volume is mapped to an actual directory point on your local filesystem and this is stored in the volume tagged as `/onedrive/data`
+
+#### 5.1 Prepare the 'config' volume
+Create the 'config' volume with the following command:
 ```bash
 docker volume create onedrive_conf
 ```

-This will create a docker volume labeled `onedrive_conf`, where all configuration of your onedrive account will be stored. You can add a custom config file and other things later.
+This will create a docker volume labeled `onedrive_conf`, where all configuration of your onedrive account will be stored. You can add a custom config file in this location at a later point in time if required.

-The second docker volume is for your data folder and is created in the next step. This volume needs to be a path to a directory on your local filesystem, and this is where your data will be stored from OneDrive. Keep in mind that:
+#### 5.2 Prepare the 'data' volume
+Create the 'data' volume with the following command:
+```bash
+docker volume create onedrive_data
+```
+
+This will create a docker volume labeled `onedrive_data` and will map to a path on your local filesystem. This is where your data from Microsoft OneDrive will be stored. Keep in mind that:

 *   The owner of this specified folder must not be root
 *   The owner of this specified folder must have permissions for its parent directory
+*   Docker will attempt to change the permissions of the volume to the user the container is configured to run as

-**NOTE:** Issues occur when this target folder is a mounted folder of an external system (NAS, SMB mount, USB Drive etc) as the 'mount' itself is owned by 'root'. If this is your use case, you *must* ensure your normal user can mount your desired target without having the target mounted by 'root'. If you do not fix this, your Docker container will fail to start with the following error message:
+**NOTE:** Issues occur when this target folder is a mounted folder of an external system (NAS, SMB mount, USB Drive etc) as the 'mount' itself is owed by 'root'. If this is your use case, you *must* ensure your normal user can mount your desired target without having the target mounted by 'root'. If you do not fix this, your Docker container will fail to start with the following error message:
 ```bash
 ROOT level privileges prohibited!
 ```

-### 3. First run
-The 'onedrive' client within the Docker container needs to be authorized with your Microsoft account. This is achieved by initially running docker in interactive mode. 
+### 6. First run of Docker container under docker and performing authorisation
+The 'onedrive' client within the container first needs to be authorised with your Microsoft account. This is achieved by initially running docker in interactive mode.

-Run the docker image with the commands below and make sure to change `ONEDRIVE_DATA_DIR` to the actual onedrive data directory on your filesystem that you wish to use (e.g. `"/home/abraunegg/OneDrive"`).
+Run the docker image with the commands below and make sure to change the value of `ONEDRIVE_DATA_DIR` to the actual onedrive data directory on your filesystem that you wish to use (e.g. `export ONEDRIVE_DATA_DIR="/home/abraunegg/OneDrive"`).
+
+**Important:** The 'target' folder of `ONEDRIVE_DATA_DIR` must exist before running the docker container. The script below will create 'ONEDRIVE_DATA_DIR' so that it exists locally for the docker volume mapping to occur.
+
+It is also a requirement that the container be run using a non-root uid and gid, you must insert a non-root UID and GID (e.g.` export ONEDRIVE_UID=1000` and export `ONEDRIVE_GID=1000`). The script below will use `id` to evaluate your system environment to use the correct values.
 ```bash
 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}" \
-    driveone/onedrive:edge
-```
-**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" \
@ -105,42 +166,41 @@ Once the 'onedrive' application is authorised, the client will automatically sta

 If the client is working as expected, you can detach from the container with Ctrl+p, Ctrl+q.

-### 4. Docker Container Status, stop, and restart
-Check if the monitor service is running
+### 7. Running the 'onedrive' container under 'docker'

+#### 7.1 Check if the monitor service is running
 ```bash
 docker ps -f name=onedrive
 ```

-Show monitor run logs
-
+#### 7.2 Show 'onedrive' runtime logs
 ```bash
 docker logs onedrive
 ```

-Stop running monitor
-
+#### 7.3 Stop running 'onedrive' container
 ```bash
 docker stop onedrive
 ```

-Resume monitor
-
+#### 7.4 Start 'onedrive' container
 ```bash
 docker start onedrive
 ```

-Remove onedrive Docker container
-
+#### 7.5 Remove 'onedrive' container
 ```bash
 docker rm -f onedrive
 ```
-## Advanced Setup

-### 5. Docker-compose
-Also supports docker-compose schemas > 3. 
-In the following example it is assumed you have a `ONEDRIVE_DATA_DIR` environment variable and a `onedrive_conf` volume. 
-However, you can also use bind mounts for the configuration folder, e.g. `export ONEDRIVE_CONF="${HOME}/OneDriveConfig"`.  
+## Advanced Usage
+
+### How to use Docker-compose
+You can utilise `docker-compose` if available on your platform if you are able to use docker compose schemas > 3.
+
+In the following example it is assumed you have a `ONEDRIVE_DATA_DIR` environment variable and have already created the `onedrive_conf` volume. 
+
+You can also use docker bind mounts for the configuration folder, e.g. `export ONEDRIVE_CONF="${HOME}/OneDriveConfig"`.

 ```
 version: "3"
@ -158,7 +218,7 @@ services:

 Note that you still have to perform step 3: First Run. 

-### 6. Edit the config
+### Editing the running configuration and using a 'config' file
 The 'onedrive' client should run in default configuration, however you can change this default configuration by placing a custom config file in the `onedrive_conf` docker volume. First download the default config from [here](https://raw.githubusercontent.com/abraunegg/onedrive/master/config)  
 Then put it into your onedrive_conf volume path, which can be found with:  

@ -170,8 +230,8 @@ Or you can map your own config folder to the config volume. Make sure to copy al

 The detailed document for the config can be found here: [Configuration](https://github.com/abraunegg/onedrive/blob/master/docs/USAGE.md#configuration)

-### 7. Sync multiple accounts
-There are many ways to do this, the easiest is probably to
+### Syncing multiple accounts
+There are many ways to do this, the easiest is probably to do the following:
 1. Create a second docker config volume (replace `Work` with your desired name):  `docker volume create onedrive_conf_Work`
 2. And start a second docker monitor container (again replace `Work` with your desired name):
 ```
@ -180,7 +240,7 @@ mkdir -p ${ONEDRIVE_DATA_DIR_WORK}
 docker run -it --restart unless-stopped --name onedrive_Work -v onedrive_conf_Work:/onedrive/conf -v "${ONEDRIVE_DATA_DIR_WORK}:/onedrive/data" driveone/onedrive:edge
 ```

-## Run or update with one script
+### Run or update the Docker container with one script
 If you are experienced with docker and onedrive, you can use the following script:

 ```bash
@ -196,7 +256,7 @@ docker inspect onedrive > /dev/null 2>&1 && docker rm -f onedrive
 docker run $firstRun --restart unless-stopped --name onedrive -v onedrive_conf:/onedrive/conf -v "${ONEDRIVE_DATA_DIR}:/onedrive/data" driveone/onedrive:edge
 ```

-## Environment Variables
+## Supported Docker Environment Variables
 | Variable | Purpose | Sample Value |
 | ---------------- | --------------------------------------------------- |:--------------------------------------------------------------------------------------------------------------------------------:|
 | <B>ONEDRIVE_UID</B> | UserID (UID) to run as  | 1000 |
@ -207,6 +267,7 @@ docker run $firstRun --restart unless-stopped --name onedrive -v onedrive_conf:/
 | <B>ONEDRIVE_RESYNC</B> | Controls "--resync" switch on onedrive sync. Default is 0 | 1 |
 | <B>ONEDRIVE_DOWNLOADONLY</B> | Controls "--download-only" switch on onedrive sync. Default is 0 | 1 |
 | <B>ONEDRIVE_UPLOADONLY</B> | Controls "--upload-only" switch on onedrive sync. Default is 0 | 1 |
+| <B>ONEDRIVE_NOREMOTEDELETE</B> | Controls "--no-remote-delete" switch on onedrive sync. Default is 0 | 1 |
 | <B>ONEDRIVE_LOGOUT</B> | Controls "--logout" switch. Default is 0 | 1 |
 | <B>ONEDRIVE_REAUTH</B> | Controls "--reauth" switch. Default is 0 | 1 |
 | <B>ONEDRIVE_AUTHFILES</B> | Controls "--auth-files" option. Default is "" | "authUrl:responseUrl" |
@ -214,7 +275,7 @@ docker run $firstRun --restart unless-stopped --name onedrive -v onedrive_conf:/
 | <B>ONEDRIVE_DISPLAY_CONFIG</B> | Controls "--display-running-config" switch on onedrive sync. Default is 0 | 1 |
 | <B>ONEDRIVE_SINGLE_DIRECTORY</B> | Controls "--single-directory" option. Default = "" | "mydir" |

-### Usage Examples
+### Environment Variables Usage Examples
 **Verbose Output:**
 ```bash
 docker container run -e ONEDRIVE_VERBOSE=1 -v onedrive_conf:/onedrive/conf -v "${ONEDRIVE_DATA_DIR}:/onedrive/data" driveone/onedrive:edge
@ -236,13 +297,25 @@ docker container run -e ONEDRIVE_RESYNC=1 -e ONEDRIVE_VERBOSE=1 -v onedrive_conf
 docker container run -it -e ONEDRIVE_LOGOUT=1 -v onedrive_conf:/onedrive/conf -v "${ONEDRIVE_DATA_DIR}:/onedrive/data" driveone/onedrive:edge
 ```

-## Build instructions
+## Building a custom Docker image
+
 ### Build Environment Requirements
 *   Build environment must have at least 1GB of memory & 2GB swap space

-There are 2 ways to validate this requirement:
-*   Modify the file `/etc/dphys-swapfile` and edit the `CONF_SWAPSIZE`, for example: `CONF_SWAPSIZE=2048`. A reboot is required to make this change effective.
-*   Dynamically allocate a swapfile for building:
+You can validate your build environment memory status with the following command:
+```text
+cat /proc/meminfo | grep -E 'MemFree|Swap'
+```
+This should result in the following similar output:
+```text
+MemFree:         3704644 kB
+SwapCached:            0 kB
+SwapTotal:       8117244 kB
+SwapFree:        8117244 kB
+```
+
+If you do not have enough swap space, you can use the following script to dynamically allocate a swapfile for building the Docker container:
+
 ```bash
 cd /var 
 sudo fallocate -l 1.5G swapfile
@ -257,31 +330,36 @@ swapon -s
 free -h
 ```

-### Building a custom Docker image
+If you are running a Raspberry Pi, you will need to edit your system configuration to increase your swapfile:
+
+*   Modify the file `/etc/dphys-swapfile` and edit the `CONF_SWAPSIZE`, for example: `CONF_SWAPSIZE=2048`. 
+
+A reboot of your Raspberry Pi is required to make this change effective.
+
+### Building and running a custom Docker image
 You can also build your own image instead of pulling the one from [hub.docker.com](https://hub.docker.com/r/driveone/onedrive):
 ```bash
 git clone https://github.com/abraunegg/onedrive
 cd onedrive
 docker build . -t local-onedrive -f contrib/docker/Dockerfile
+docker container run -v onedrive_conf:/onedrive/conf -v "${ONEDRIVE_DATA_DIR}:/onedrive/data" local-onedrive:latest
 ```

-There are alternate, smaller images available by building
-Dockerfile-debian or Dockerfile-alpine.  These [multi-stage builder pattern](https://docs.docker.com/develop/develop-images/multistage-build/)
-Dockerfiles require Docker version at least 17.05.
+There are alternate, smaller images available by using `Dockerfile-debian` or `Dockerfile-alpine`. These [multi-stage builder pattern](https://docs.docker.com/develop/develop-images/multistage-build/) Dockerfiles require Docker version at least 17.05.

-#### How to build and run a custom Docker image based on Debian
+### How to build and run a custom Docker image based on Debian
 ``` bash
 docker build . -t local-ondrive-debian -f contrib/docker/Dockerfile-debian
 docker container run -v onedrive_conf:/onedrive/conf -v "${ONEDRIVE_DATA_DIR}:/onedrive/data" local-ondrive-debian:latest
 ```

-#### How to build and run a custom Docker image based on Alpine Linux
+### How to build and run a custom Docker image based on Alpine Linux
 ``` bash
 docker build . -t local-ondrive-alpine -f contrib/docker/Dockerfile-alpine
 docker container run -v onedrive_conf:/onedrive/conf -v "${ONEDRIVE_DATA_DIR}:/onedrive/data" local-ondrive-alpine:latest
 ```

-#### How to build and run a custom Docker image for ARMHF (Raspberry Pi)
+### How to build and run a custom Docker image for ARMHF (Raspberry Pi)
 Compatible with:
 *    Raspberry Pi
 *    Raspberry Pi 2
@ -293,13 +371,12 @@ docker build . -t local-onedrive-armhf -f contrib/docker/Dockerfile-debian
 docker container run -v onedrive_conf:/onedrive/conf -v "${ONEDRIVE_DATA_DIR}:/onedrive/data" local-onedrive-armhf:latest
 ```

-#### How to build and run a custom Docker image for AARCH64 Platforms
+### How to build and run a custom Docker image for AARCH64 Platforms
 ``` bash
 docker build . -t local-onedrive-aarch64 -f contrib/docker/Dockerfile-debian
 docker container run -v onedrive_conf:/onedrive/conf -v "${ONEDRIVE_DATA_DIR}:/onedrive/data" local-onedrive-aarch64:latest
 ```
-
-#### How to support double-byte languages
+### How to support double-byte languages
 In some geographic regions, you may need to change and/or update the locale specification of the Docker container to better support the local language used for your local filesystem. To do this, follow the example below:
 ```
 FROM driveone/onedrive
@ -316,4 +393,4 @@ RUN echo "ja_JP.UTF-8 UTF-8" > /etc/locale.gen && \

 ENV LC_ALL ja_JP.UTF-8
 ```
-The above example changes the Docker container to support Japanese. To support your local language, change `ja_JP.UTF-8` to the required entry.
+The above example changes the Docker container to support Japanese. To support your local language, change `ja_JP.UTF-8` to the required entry.
--- a/docs/INSTALL.md
+++ b/docs/INSTALL.md
@ -13,7 +13,7 @@ Distribution packages may be of an older release when compared to the latest rel
 | Alpine Linux                    | [onedrive](https://pkgs.alpinelinux.org/packages?name=onedrive&branch=edge)  |<a href="https://pkgs.alpinelinux.org/packages?name=onedrive&branch=edge"><img src="https://repology.org/badge/version-for-repo/alpine_edge/onedrive.svg?header=" alt="Alpine Linux Edge package" width="46" height="20"></a>|❌|✔|❌|✔ | |
 | Arch Linux<br><br>Manjaro Linux | [onedrive-abraunegg](https://aur.archlinux.org/packages/onedrive-abraunegg/) |<a href="https://aur.archlinux.org/packages/onedrive-abraunegg"><img src="https://repology.org/badge/version-for-repo/aur/onedrive-abraunegg.svg?header=" alt="AUR package" width="46" height="20"></a>|✔|✔|✔|✔ | Install via: `pamac build onedrive-abraunegg` from the Arch Linux User Repository (AUR)<br><br>**Note:** If asked regarding a provider for 'd-runtime' and 'd-compiler', select 'liblphobos' and 'ldc'<br><br>**Note:** System must have at least 1GB of memory & 1GB swap space
 | Debian 11                       | [onedrive](https://packages.debian.org/bullseye/source/onedrive)             |<a href="https://packages.debian.org/bullseye/source/onedrive"><img src="https://repology.org/badge/version-for-repo/debian_11/onedrive.svg?header=" alt="Debian 11 package" width="46" height="20"></a>|✔|✔|✔|✔| **Note:** Do not install from Debian Package Repositories<br><br>It is recommended that for Debian 11 that you install from OpenSuSE Build Service using the Debian Package Install [Instructions](ubuntu-package-install.md) |
-| Debian 12                       | [onedrive](https://packages.debian.org/bookworm/source/onedrive)             |<a href="https://packages.debian.org/bookworm/source/onedrive"><img src="https://repology.org/badge/version-for-repo/debian_12/onedrive.svg?header=" alt="Debian 12 package" width="46" height="20"></a>|✔|✔|✔|✔| Install via: `sudo apt install --no-install-recommends --no-install-suggests onedrive` |
+| Debian 12                       | [onedrive](https://packages.debian.org/bookworm/source/onedrive)             |<a href="https://packages.debian.org/bookworm/source/onedrive"><img src="https://repology.org/badge/version-for-repo/debian_12/onedrive.svg?header=" alt="Debian 12 package" width="46" height="20"></a>|✔|✔|✔|✔| **Note:** Do not install from Debian Package Repositories<br><br>It is recommended that for Debian 12 that you install from OpenSuSE Build Service using the Debian Package Install [Instructions](ubuntu-package-install.md) |
 | Fedora                          | [onedrive](https://koji.fedoraproject.org/koji/packageinfo?packageID=26044)  |<a href="https://koji.fedoraproject.org/koji/packageinfo?packageID=26044"><img src="https://repology.org/badge/version-for-repo/fedora_rawhide/onedrive.svg?header=" alt="Fedora Rawhide package" width="46" height="20"></a>|✔|✔|✔|✔| |
 | Gentoo                          | [onedrive](https://gpo.zugaina.org/net-misc/onedrive)                        | No API Available |✔|✔|❌|❌| |
 | Homebrew                        | [onedrive](https://formulae.brew.sh/formula/onedrive)                        | <a href="https://formulae.brew.sh/formula/onedrive"><img src="https://repology.org/badge/version-for-repo/homebrew/onedrive.svg?header=" alt="Homebrew package" width="46" height="20"></a> |❌|✔|❌|❌| |
@ -71,7 +71,7 @@ Ubuntu Linux 18.x LTS reached the end of its five-year LTS window on May 31th 20
 ### Dependencies: Debian 9
 Debian 9 reached the end of its five-year support window on June 30th 2022 and is no longer supported.

-### Dependencies: Ubuntu 20.x -> Ubuntu 23.x / Debian 10 -> Debian 11 - x86_64
+### Dependencies: Ubuntu 20.x -> Ubuntu 23.x / Debian 10 -> Debian 12 - x86_64
 These dependencies are also applicable for all Ubuntu based distributions such as:
 *   Lubuntu
 *   Linux Mint
@ -121,7 +121,7 @@ For notifications the following is also necessary:
 sudo pacman -S libnotify
 ```

-### Dependencies: Raspbian (ARMHF) and Ubuntu 22.x / Debian 11 / Raspbian (ARM64)
+### Dependencies: Raspbian (ARMHF) and Ubuntu 22.x / Debian 11 / Debian 12 / Raspbian (ARM64)
 **Note:** The minimum LDC compiler version required to compile this application is now 1.18.0, which is not available for Debian Buster or distributions based on Debian Buster. You are advised to first upgrade your platform distribution to one that is based on Debian Bullseye (Debian 11) or later.

 These instructions were validated using:
--- a/docs/Podman.md
+++ b/docs/Podman.md
@ -15,28 +15,90 @@ This client can be run as a Podman container, with 3 available container base op
 These containers offer a simple monitoring-mode service for the OneDrive Client for Linux.

 The instructions below have been validated on:
-*   Fedora 35
+*   Fedora 38

-The instructions below will utilise the 'latest' tag, however this can be substituted for any of the other docker tags from the table above if desired.
+The instructions below will utilise the 'edge' tag, however this can be substituted for any of the other docker tags such as 'latest' from the table above if desired.
+
+The 'edge' Docker Container will align closer to all documentation and features, where as 'latest' is the release version from a static point in time. The 'latest' tag however may contain bugs and/or issues that will have been fixed, and those fixes are contained in 'edge'.

 Additionally there are specific version release tags for each release. Refer to https://hub.docker.com/r/driveone/onedrive/tags for any other Docker tags you may be interested in.

-**Note:** The below instructions for podman have only been tested as the root user while running the containers themselves as non-root users.
+**Note:** The below instructions for podman has been tested and validated when logging into the system as an unprivileged user (non 'root' user).

-## Basic Setup
-### 0. Install podman using your distribution platform's instructions if not already installed
-1.  Ensure that SELinux has been disabled on your system. A reboot may be required to ensure that this is correctly disabled.
-2.  Install Podman as per requried for your platform
-3.  Obtain your normal, non-root user UID and GID by using the `id` command or select another non-root id to run the container as
+## High Level Configuration Steps
+1. Install 'podman' as per your distribution platform's instructions if not already installed.
+2. Disable 'SELinux' as per your distribution platform's instructions
+3. Test 'podman' by running a test container
+4. Prepare the required podman volumes to store the configuration and data
+5. Run the 'onedrive' container and perform authorisation
+6. Running the 'onedrive' container under 'podman'

-**NOTE:** SELinux context needs to be configured or disabled for Podman to be able to write to OneDrive host directory.
+## Configuration Steps

-### 1.1 Prepare data volume
-The container requries 2 Podman volumes:
+### 1. Install 'podman' on your platform
+Install 'podman' as per your distribution platform's instructions if not already installed.
+
+### 2. Disable SELinux on your platform
+In order to run the Docker container under 'podman', SELinux must be disabled. Without doing this, when the application is authenticated in the steps below, the following error will be presented:
+```text
+ERROR: The local file system returned an error with the following message:
+  Error Message:    /onedrive/conf/refresh_token: Permission denied
+
+The database cannot be opened. Please check the permissions of ~/.config/onedrive/items.sqlite3
+```
+The only known work-around for the above problem at present is to disable SELinux. Please refer to your distribution platform's instructions on how to perform this step.
+
+* Fedora: https://docs.fedoraproject.org/en-US/quick-docs/selinux-changing-states-and-modes/#_disabling_selinux
+* Red Hat Enterprise Linux: https://access.redhat.com/solutions/3176
+
+Post disabling SELinux and reboot your system, confirm that `getenforce` returns `Disabled`:
+```text
+$ getenforce
+Disabled
+```
+
+If you are still experiencing permission issues despite disabling SELinux, please read https://www.redhat.com/sysadmin/container-permission-denied-errors
+
+### 3. Test 'podman' on your platform
+Test that 'podman' is operational for your 'non-root' user, as per below:
+```bash
+[alex@fedora38-podman ~]$ podman pull fedora
+Resolved "fedora" as an alias (/etc/containers/registries.conf.d/000-shortnames.conf)
+Trying to pull registry.fedoraproject.org/fedora:latest...
+Getting image source signatures
+Copying blob b30887322388 done   | 
+Copying config a1cd3cbf8a done   | 
+Writing manifest to image destination
+a1cd3cbf8adaa422629f2fcdc629fd9297138910a467b11c66e5ddb2c2753dff
+[alex@fedora38-podman ~]$ podman run fedora /bin/echo "Welcome to the Podman World"
+Welcome to the Podman World
+[alex@fedora38-podman ~]$ 
+```
+
+### 4. Configure the required podman volumes
+The 'onedrive' Docker container requires 2 podman volumes to operate:
 *    Config Volume
 *    Data Volume

-The first volume is for your data folder and is created in the next step. This volume needs to be a path to a directory on your local filesystem, and this is where your data will be stored from OneDrive. Keep in mind that:
+The first volume is the configuration volume that stores all the applicable application configuration + current runtime state. In a non-containerised environment, this normally resides in `~/.config/onedrive` - in a containerised environment this is stored in the volume tagged as `/onedrive/conf`
+
+The second volume is the data volume, where all your data from Microsoft OneDrive is stored locally. This volume is mapped to an actual directory point on your local filesystem and this is stored in the volume tagged as `/onedrive/data`
+
+#### 4.1 Prepare the 'config' volume
+Create the 'config' volume with the following command:
+```bash
+podman volume create onedrive_conf
+```
+
+This will create a podman volume labeled `onedrive_conf`, where all configuration of your onedrive account will be stored. You can add a custom config file in this location at a later point in time if required.
+
+#### 4.2 Prepare the 'data' volume
+Create the 'data' volume with the following command:
+```bash
+podman volume create onedrive_data
+```
+
+This will create a podman volume labeled `onedrive_data` and will map to a path on your local filesystem. This is where your data from Microsoft OneDrive will be stored. Keep in mind that:

 *   The owner of this specified folder must not be root
 *   Podman will attempt to change the permissions of the volume to the user the container is configured to run as
@ -46,47 +108,54 @@ The first volume is for your data folder and is created in the next step. This v
 ROOT level privileges prohibited!
 ```

-### 1.2 Prepare config volume
-Although not required, you can prepare the config volume before starting the container. Otherwise it will be created automatically during initial startup of the container.
+### 5. First run of Docker container under podman and performing authorisation
+The 'onedrive' client within the container first needs to be authorised with your Microsoft account. This is achieved by initially running podman in interactive mode.

-Create the config volume with the following command:
-```bash
-podman volume create onedrive_conf
-```
+Run the podman image with the commands below and make sure to change the value of `ONEDRIVE_DATA_DIR` to the actual onedrive data directory on your filesystem that you wish to use (e.g. `export ONEDRIVE_DATA_DIR="/home/abraunegg/OneDrive"`).

-This will create a podman volume labeled `onedrive_conf`, where all configuration of your onedrive account will be stored. You can add a custom config file and other things later.
-
-### 2. First run
-The 'onedrive' client within the container needs to be authorized with your Microsoft account. This is achieved by initially running podman in interactive mode. 
-
-Run the podman image with the commands below and make sure to change `ONEDRIVE_DATA_DIR` to the actual onedrive data directory on your filesystem that you wish to use (e.g. `"/home/abraunegg/OneDrive"`).
-
-It is a requirement that the container be run using a non-root uid and gid, you must insert a non-root UID and GID (e.g.` export ONEDRIVE_UID=1000` and export `ONEDRIVE_GID=1000`). 
+**Important:** The 'target' folder of `ONEDRIVE_DATA_DIR` must exist before running the podman container. The script below will create 'ONEDRIVE_DATA_DIR' so that it exists locally for the podman volume mapping to occur.

+It is also a requirement that the container be run using a non-root uid and gid, you must insert a non-root UID and GID (e.g.` export ONEDRIVE_UID=1000` and export `ONEDRIVE_GID=1000`). The script below will use `id` to evaluate your system environment to use the correct values.
 ```bash
 export ONEDRIVE_DATA_DIR="${HOME}/OneDrive"
-export ONEDRIVE_UID=1000
-export ONEDRIVE_GID=1000
+export ONEDRIVE_UID=`id -u`
+export ONEDRIVE_GID=`id -g`
 mkdir -p ${ONEDRIVE_DATA_DIR}
 podman run -it --name onedrive --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" \
    -v onedrive_conf:/onedrive/conf:U,Z \
    -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" \
-    driveone/onedrive:latest
+    driveone/onedrive:edge
 ```
-**Important:** The 'target' folder of `ONEDRIVE_DATA_DIR` must exist before running the podman container

-**If you plan to use podmans built in auto-updating of container images described in step 5, you must pass an additional argument to set a label during the first run.**
+**Important:** In some scenarios, 'podman' sets the configuration and data directories to a different UID & GID as specified. To resolve this situation, you must run 'podman' with the `--userns=keep-id` flag to ensure 'podman' uses the UID and GID as specified. The updated script example when using `--userns=keep-id` is below:

-**Important:** In some scenarios, 'podman' sets the configuration and data directories to a different UID & GID as specified. To resolve this situation, you must run 'podman' with the `--userns=keep-id` flag to ensure 'podman' uses the UID and GID as specified.
-
-The run command would look instead look like as follows:
-```
+```bash
+export ONEDRIVE_DATA_DIR="${HOME}/OneDrive"
+export ONEDRIVE_UID=`id -u`
+export ONEDRIVE_GID=`id -g`
+mkdir -p ${ONEDRIVE_DATA_DIR}
 podman run -it --name onedrive --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" \
+    --userns=keep-id \
    -v onedrive_conf:/onedrive/conf:U,Z \
-    -v "onedrive-test-data:/onedrive/data:U,Z" \
+    -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" \
+    driveone/onedrive:edge
+```
+
+
+**Important:** If you plan to use the 'podman' built in auto-updating of container images described in 'Systemd Service & Auto Updating' below, you must pass an additional argument to set a label during the first run. The updated script example to support auto-updating of container images is below:
+
+```bash
+export ONEDRIVE_DATA_DIR="${HOME}/OneDrive"
+export ONEDRIVE_UID=`id -u`
+export ONEDRIVE_GID=`id -g`
+mkdir -p ${ONEDRIVE_DATA_DIR}
+podman run -it --name onedrive --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" \
+    --userns=keep-id \
+    -v onedrive_conf:/onedrive/conf:U,Z \
+    -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" \
    -e PODMAN=1 \
-    --label "io.containers.autoupdate=image"
-    driveone/onedrive:latest
+    --label "io.containers.autoupdate=image" \
+    driveone/onedrive:edge
 ```

 When the Podman container successfully starts:
@ -99,41 +168,39 @@ Once the 'onedrive' application is authorised, the client will automatically sta

 If the client is working as expected, you can detach from the container with Ctrl+p, Ctrl+q.

-### 4. Podman Container Status, stop, and restart
-Check if the monitor service is running
+### 6. Running the 'onedrive' container under 'podman'

+#### 6.1 Check if the monitor service is running
 ```bash
 podman ps -f name=onedrive
 ```

-Show monitor run logs
-
+#### 6.2 Show 'onedrive' runtime logs
 ```bash
 podman logs onedrive
 ```

-Stop running monitor
-
+#### 6.3 Stop running 'onedrive' container
 ```bash
 podman stop onedrive
 ```

-Resume monitor
-
+#### 6.4 Start 'onedrive' container
 ```bash
 podman start onedrive
 ```

-Remove onedrive container
-
+#### 6.5 Remove 'onedrive' container
 ```bash
 podman rm -f onedrive
 ```
-## Advanced Setup

-### 5. Systemd Service & Auto Updating

-Podman supports running containers as a systemd service and also auto updating of the container images. Using the existing running container you can generate a systemd unit file to be installed by the **root** user. To have your container image auto-update with podman, it must first be created with the label `"io.containers.autoupdate=image"` mentioned in step 2.
+## Advanced Usage
+
+### Systemd Service & Auto Updating
+
+Podman supports running containers as a systemd service and also auto updating of the container images. Using the existing running container you can generate a systemd unit file to be installed by the **root** user. To have your container image auto-update with podman, it must first be created with the label `"io.containers.autoupdate=image"` mentioned in step 5 above.

 ```
 cd /tmp
@ -179,7 +246,7 @@ systemctl start podman-auto-update.timer
 systemctl list-timers --all
 ```

-### 6. Edit the config
+### Editing the running configuration and using a 'config' file
 The 'onedrive' client should run in default configuration, however you can change this default configuration by placing a custom config file in the `onedrive_conf` podman volume. First download the default config from [here](https://raw.githubusercontent.com/abraunegg/onedrive/master/config)  
 Then put it into your onedrive_conf volume path, which can be found with:  

@ -190,21 +257,26 @@ Or you can map your own config folder to the config volume. Make sure to copy al

 The detailed document for the config can be found here: [Configuration](https://github.com/abraunegg/onedrive/blob/master/docs/USAGE.md#configuration)

-### 7. Sync multiple accounts
-There are many ways to do this, the easiest is probably to
-1. Create a second podman config volume (replace `Work` with your desired name):  `podman volume create onedrive_conf_Work`
-2. And start a second podman monitor container (again replace `Work` with your desired name):
-```
+### Syncing multiple accounts
+There are many ways to do this, the easiest is probably to do the following:
+1. Create a second podman config volume (replace `work` with your desired name):  `podman volume create onedrive_conf_work`
+2. And start a second podman monitor container (again replace `work` with your desired name):
+
+```bash
 export ONEDRIVE_DATA_DIR_WORK="/home/abraunegg/OneDriveWork"
+export ONEDRIVE_UID=`id -u`
+export ONEDRIVE_GID=`id -g`
 mkdir -p ${ONEDRIVE_DATA_DIR_WORK}
-podman run -it --restart unless-stopped --name onedrive_work \
-   -v onedrive_conf_Work:/onedrive/conf \
-   -v "${ONEDRIVE_DATA_DIR_WORK}:/onedrive/data" \
-   --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" \
-   driveone/onedrive:latest
+podman run -it --name onedrive_work --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" \
+    --userns=keep-id \
+    -v onedrive_conf_work:/onedrive/conf:U,Z \
+    -v "${ONEDRIVE_DATA_DIR_WORK}:/onedrive/data:U,Z" \
+    -e PODMAN=1 \
+    --label "io.containers.autoupdate=image" \
+    driveone/onedrive:edge
 ```

-## Environment Variables
+## Supported Podman Environment Variables
 | Variable | Purpose | Sample Value |
 | ---------------- | --------------------------------------------------- |:-------------:|
 | <B>ONEDRIVE_UID</B> | UserID (UID) to run as  | 1000 |
@ -215,6 +287,7 @@ podman run -it --restart unless-stopped --name onedrive_work \
 | <B>ONEDRIVE_RESYNC</B> | Controls "--resync" switch on onedrive sync. Default is 0 | 1 |
 | <B>ONEDRIVE_DOWNLOADONLY</B> | Controls "--download-only" switch on onedrive sync. Default is 0 | 1 |
 | <B>ONEDRIVE_UPLOADONLY</B> | Controls "--upload-only" switch on onedrive sync. Default is 0 | 1 |
+| <B>ONEDRIVE_NOREMOTEDELETE</B> | Controls "--no-remote-delete" switch on onedrive sync. Default is 0 | 1 |
 | <B>ONEDRIVE_LOGOUT</B> | Controls "--logout" switch. Default is 0 | 1 |
 | <B>ONEDRIVE_REAUTH</B> | Controls "--reauth" switch. Default is 0 | 1 |
 | <B>ONEDRIVE_AUTHFILES</B> | Controls "--auth-files" option. Default is "" | "authUrl:responseUrl" |
@ -222,30 +295,29 @@ podman run -it --restart unless-stopped --name onedrive_work \
 | <B>ONEDRIVE_DISPLAY_CONFIG</B> | Controls "--display-running-config" switch on onedrive sync. Default is 0 | 1 |
 | <B>ONEDRIVE_SINGLE_DIRECTORY</B> | Controls "--single-directory" option. Default = "" | "mydir" |

-### Usage Examples
+### Environment Variables Usage Examples
 **Verbose Output:**
 ```bash
-podman run -e ONEDRIVE_VERBOSE=1 -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" driveone/onedrive:latest
+podman run -e ONEDRIVE_VERBOSE=1 -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" driveone/onedrive:edge
 ```
 **Debug Output:**
 ```bash
-podman run -e ONEDRIVE_DEBUG=1 -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" driveone/onedrive:latest
+podman run -e ONEDRIVE_DEBUG=1 -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" driveone/onedrive:edge
 ```
 **Perform a --resync:**
 ```bash
-podman run -e ONEDRIVE_RESYNC=1 -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" driveone/onedrive:latest
+podman run -e ONEDRIVE_RESYNC=1 -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" driveone/onedrive:edge
 ```
 **Perform a --resync and --verbose:**
 ```bash
-podman run -e ONEDRIVE_RESYNC=1 -e ONEDRIVE_VERBOSE=1 -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" driveone/onedrive:latest
+podman run -e ONEDRIVE_RESYNC=1 -e ONEDRIVE_VERBOSE=1 -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" driveone/onedrive:edge
 ```
 **Perform a --logout and re-authenticate:**
 ```bash
-podman run -it -e ONEDRIVE_LOGOUT=1 -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" driveone/onedrive:latest
+podman run -it -e ONEDRIVE_LOGOUT=1 -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" driveone/onedrive:edge
 ```

-## Build instructions
-### Building a custom Podman image
+## Building a custom Podman image
 You can also build your own image instead of pulling the one from [hub.docker.com](https://hub.docker.com/r/driveone/onedrive):
 ```bash
 git clone https://github.com/abraunegg/onedrive
@ -257,19 +329,19 @@ There are alternate, smaller images available by building
 Dockerfile-debian or Dockerfile-alpine.  These [multi-stage builder pattern](https://docs.docker.com/develop/develop-images/multistage-build/)
 Dockerfiles require Docker version at least 17.05.

-#### How to build and run a custom Podman image based on Debian
+### How to build and run a custom Podman image based on Debian
 ``` bash
 podman build . -t local-ondrive-debian -f contrib/docker/Dockerfile-debian
-podman run -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" local-ondrive-debian:latest
+podman run -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" --userns=keep-id local-ondrive-debian:latest
 ```

-#### How to build and run a custom Podman image based on Alpine Linux
+### How to build and run a custom Podman image based on Alpine Linux
 ``` bash
 podman build . -t local-ondrive-alpine -f contrib/docker/Dockerfile-alpine
-podman run -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" local-ondrive-alpine:latest
+podman run -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" --userns=keep-id local-ondrive-alpine:latest
 ```

-#### How to build and run a custom Podman image for ARMHF (Raspberry Pi)
+### How to build and run a custom Podman image for ARMHF (Raspberry Pi)
 Compatible with:
 *    Raspberry Pi
 *    Raspberry Pi 2
@ -278,11 +350,11 @@ Compatible with:
 *    Raspberry Pi 4
 ``` bash
 podman build . -t local-onedrive-armhf -f contrib/docker/Dockerfile-debian
-podman run -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" local-onedrive-armhf:latest
+podman run -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" --userns=keep-id local-onedrive-armhf:latest
 ```

-#### How to build and run a custom Podman image for AARCH64 Platforms
+### How to build and run a custom Podman image for AARCH64 Platforms
 ``` bash
 podman build . -t local-onedrive-aarch64 -f contrib/docker/Dockerfile-debian
-podman run -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" local-onedrive-aarch64:latest
+podman run -v onedrive_conf:/onedrive/conf:U,Z -v "${ONEDRIVE_DATA_DIR}:/onedrive/data:U,Z" --user "${ONEDRIVE_UID}:${ONEDRIVE_GID}" --userns=keep-id local-onedrive-aarch64:latest
 ```
--- a/docs/USAGE.md
+++ b/docs/USAGE.md
@ -35,6 +35,7 @@ Before reading this document, please ensure you are running application version
    + [min_notify_changes](#min_notify_changes)
    + [operation_timeout](#operation_timeout)
    + [ip_protocol_version](#ip_protocol_version)
+	+ [classify_as_big_delete](#classify_as_big_delete)
  * [Configuring the client for 'single tenant application' use](#configuring-the-client-for-single-tenant-application-use)
  * [Configuring the client to use older 'skilion' application identifier](#configuring-the-client-to-use-older-skilion-application-identifier)
 - [Frequently Asked Configuration Questions](#frequently-asked-configuration-questions)
@ -220,7 +221,7 @@ In some cases it may be desirable to 'upload only' to OneDrive. To do this use t
 ```text
 onedrive --synchronize --upload-only
 ```
-**Note:** If a file or folder is present on OneDrive, that was previously sycned and now does not exist locally, that item it will be removed from OneDrive. If the data on OneDrive should be kept, the following should be used:
+**Note:** If a file or folder is present on OneDrive, that was previously synced and now does not exist locally, that item it will be removed from OneDrive. If the data on OneDrive should be kept, the following should be used:
 ```text
 onedrive --synchronize --upload-only --no-remote-delete
 ```
@ -621,7 +622,7 @@ Patterns are case insensitive. `*` and `?` [wildcards characters](https://techne

 Files can be skipped in the following fashion:
 *   Specify a wildcard, eg: '*.txt' (skip all txt files)
-*   Explicitly specify the filename and it's full path relative to your sync_dir, eg: 'path/to/file/filename.ext'
+*   Explicitly specify the filename and it's full path relative to your sync_dir, eg: '/path/to/file/filename.ext'
 *   Explicitly specify the filename only and skip every instance of this filename, eg: 'filename.ext'

 By default, the following files will be skipped:
@ -637,7 +638,7 @@ Example:
 # For explanations of all config options below see docs/USAGE.md or the man page.
 #
 # sync_dir = "~/OneDrive"
-skip_file = "~*|Documents/OneNote*|Documents/config.xlaunch|myfile.ext"
+skip_file = "~*|/Documents/OneNote*|/Documents/config.xlaunch|myfile.ext|/Documents/keepass.kdbx"
 # monitor_interval = "300"
 # skip_dir = ""
 # log_dir = "/var/log/onedrive/"
@ -648,10 +649,11 @@ skip_file = "~*|Documents/OneNote*|Documents/config.xlaunch|myfile.ext"
 skip_file = "~*|.~*|*.tmp|*.swp"
 skip_file = "*.blah"
 skip_file = "never_sync.file"
+skip_file = "/Documents/keepass.kdbx"
 ```
 This will be interpreted the same as:
 ```text
-skip_file = "~*|.~*|*.tmp|*.swp|*.blah|never_sync.file"
+skip_file = "~*|.~*|*.tmp|*.swp|*.blah|never_sync.file|/Documents/keepass.kdbx"
 ```

 **Note:** after changing `skip_file`, you must perform a full re-synchronization by adding `--resync` to your existing command line - for example: `onedrive --synchronize --resync`
@ -681,6 +683,7 @@ monitor_interval = "600"
 # min_notify_changes = "5"
 # monitor_log_frequency = "6"
 ```
+**Note:** It is strongly advised you do not use a value of less than 300 seconds for 'monitor_interval'. Using a value less than 300 means your application will be constantly needlessly checking OneDrive online for changes. Future versions of the application may enforce the checking of this minimum value.

 #### monitor_fullscan_frequency
 This configuration option controls the number of 'monitor_interval' iterations between when a full scan of your data is performed to ensure data integrity and consistency.
@ -763,6 +766,26 @@ ip_protocol_version = "1"
 * A value of 1 will mean the client will use IPv4 only.
 * A value of 2 will mean the client will use IPv6 only.

+#### classify_as_big_delete
+This configuration option will help prevent the online deletion of files and folders online, when the directory that has been deleted contains more items than the specified value.
+
+By default, this value is 1000 which will count files and folders as children of the directory that has been deleted.
+
+To change this value, configure the following in your config file:
+```text
+# monitor_fullscan_frequency = "12"
+# sync_root_files = "false"
+classify_as_big_delete = "3000"
+# user_agent = ""
+# remove_source_files = "false"
+```
+
+**Note:**
+* This option only looks at Directories. It has zero effect on deleting files located in your 'sync_dir' root
+* This option (in v2.4.x and below) only gets activated when using `--monitor`. In `--synchronize` mode it is ignored as it is assumed you performed that desired operation before you started your next manual sync with OneDrive.
+* Be sensible with setting this value - do not use a low value such as '1' as this will prevent you from syncing your data each and every time you delete a single file.
+
+
 #### Configuring the client for 'single tenant application' use
 In some instances when using OneDrive Business Accounts, depending on the Azure organisational configuration, it will be necessary to configure the client as a 'single tenant application'.
 To configure this, after creating the application on your Azure tenant, update the 'config' file with the tenant name (not the GUID) and the newly created Application ID, then this will be used for the authentication process.
@ -986,7 +1009,7 @@ A webhook can be optionally enabled in the monitor mode to allow the onedrive pr

 To enable this feature, you need to configure the following options in the config file:

-```
+```text
 webhook_enabled = "true"
 webhook_public_url = "<public-facing url to reach your webhook>"
 ```
@ -997,10 +1020,11 @@ Setting `webhook_enabled` to `true` enables the webhook in 'monitor' mode. The o

 For example, below is a nginx config snippet to proxy traffic into the webhook:

-```
+```text
 server {
 	listen 80;
 	location /webhooks/onedrive {
+		proxy_http_version 1.1;
 		proxy_pass http://127.0.0.1:8888;
 	}
 }
@ -1008,6 +1032,29 @@ server {

 With nginx running, you can configure `webhook_public_url` to `https://<your_host>/webhooks/onedrive`.

+If you receive this application error:
+```text
+Subscription validation request failed. Response must exactly match validationToken query parameter.
+```
+The most likely cause for this error will be your nginx configuration. To resolve, potentially investigate the following configuration for nginx:
+
+```text
+server {
+	listen 80;
+	location /webhooks/onedrive {
+		proxy_set_header X-Forwarded-For $proxy_add_x_forwarded_for;
+		proxy_set_header X-Original-Request-URI $request_uri;
+		proxy_read_timeout 300s;
+		proxy_connect_timeout 75s;
+		proxy_buffering off;
+		proxy_http_version 1.1;
+		proxy_pass http://127.0.0.1:8888;
+	}
+}
+```
+
+For any further nginx configuration assistance, please refer to: https://docs.nginx.com/
+
 ### More webhook configuration options

 Below options can be optionally configured. The default is usually good enough.
--- a/docs/application-security.md
+++ b/docs/application-security.md
@ -1,12 +1,27 @@
 # OneDrive Client for Linux Application Security
-This document details the application security used, and provides details for users on changing these security options.
+This document details the following information:

+* Why is this application an 'unverified publisher'?
+* Application Security and Permission Scopes
+* How to change Permission Scopes
+* How to review your existing application access consent
+
+## Why is this application an 'unverified publisher'?
+Publisher Verification, as per the Microsoft [process](https://learn.microsoft.com/en-us/azure/active-directory/develop/publisher-verification-overview) has actually been configured, and, actually has been verified!
+
+### Verified Publisher Configuration Evidence
+As per the image below, the Azure portal shows that the 'Publisher Domain' has actually been verified:
+![confirmed_verified_publisher](./images/confirmed_verified_publisher.jpg)
+
+* The 'Publisher Domain' is: https://abraunegg.github.io/
+* The required 'Microsoft Identity Association' is: https://abraunegg.github.io/.well-known/microsoft-identity-association.json
+
+## Application Security and Permission Scopes
 There are 2 main components regarding security for this application:
 * Azure Application Permissions
 * User Authentication Permissions

-## Default Application Security
-Security options should follow the security principal of 'least privilege':
+Keeping this in mind, security options should follow the security principal of 'least privilege':
 > The principle that a security architecture should be designed so that each entity 
 > is granted the minimum system resources and authorizations that the entity needs 
 > to perform its function.
@ -28,6 +43,8 @@ As such, the following API permissions are used by default:

 ### Default User Authentication Permissions

+When a user authenticates with Microsoft OneDrive, additional account permissions are provided by service to give the user specific access to their data. These are delegated permissions provided by the platform:
+
 | API / Permissions name | Type | Description | Admin consent required |
 |---|---|---|---|
 | Files.ReadWrite | Delegated | Have full access to user files | No |
@ -35,7 +52,7 @@ As such, the following API permissions are used by default:
 | Sites.ReadWrite.All   | Delegated | Have full access to all items in all site collections | No |
 | offline_access   | Delegated | Maintain access to data you have given it access to | No |

-When these delegated API permissions are combined, these provide the effective authentication scope for the OneDrive Client for Linux to access your data. The effective 'default' permissions will be:
+When these delegated API permissions are combined, these provide the effective authentication scope for the OneDrive Client for Linux to access your data. The resulting effective 'default' permissions will be:

 | API / Permissions name | Type | Description | Admin consent required |
 |---|---|---|---|
--- a/docs/images/confirmed_verified_publisher.jpg
+++ b/docs/images/confirmed_verified_publisher.jpg
--- a/docs/privacy-policy.md
+++ b/docs/privacy-policy.md
@ -0,0 +1,65 @@
+# Privacy Policy
+Effective Date: May 16 2018
+
+## Introduction
+
+This Privacy Policy outlines how OneDrive Client for Linux ("we," "our," or "us") collects, uses, and protects information when you use our software ("OneDrive Client for Linux"). We respect your privacy and are committed to ensuring the confidentiality and security of any information you provide while using the Software.
+
+## Information We Do Not Collect
+
+We want to be transparent about the fact that we do not collect any personal data, usage data, or tracking data through the Software. This means:
+
+1. **No Personal Data**: We do not collect any information that can be used to personally identify you, such as your name, email address, phone number, or physical address.
+
+2. **No Usage Data**: We do not collect data about how you use the Software, such as the features you use, the duration of your sessions, or any interactions within the Software.
+
+3. **No Tracking Data**: We do not use cookies or similar tracking technologies to monitor your online behavior or track your activities across websites or apps.
+
+## How We Use Your Information
+
+Since we do not collect any personal, usage, or tracking data, there is no information for us to use for any purpose.
+
+## Third-Party Services
+
+The Software may include links to third-party websites or services, but we do not have control over the privacy practices or content of these third-party services. We encourage you to review the privacy policies of any third-party services you access through the Software.
+
+## Children's Privacy
+
+Since we do not collect any personal, usage, or tracking data, there is no restriction on the use of this application by anyone under the age of 18.
+
+## Information You Choose to Share
+
+While we do not collect personal data, usage data, or tracking data through the Software, there may be instances where you voluntarily choose to share information with us, particularly when submitting bug reports. These bug reports may contain sensitive information such as account details, file names, and directory names. It's important to note that these details are included in the logs and debug logs solely for the purpose of diagnosing and resolving technical issues with the Software. 
+
+We want to emphasize that, even in these cases, we do not have access to your actual data. The logs and debug logs provided in bug reports are used exclusively for technical troubleshooting and debugging purposes. We take measures to treat this information with the utmost care, and it is only accessible to our technical support and development teams. We do not use this information for any other purpose, and we have strict security measures in place to protect it.
+
+## Protecting Your Sensitive Data
+
+We are committed to safeguarding your sensitive data and maintaining its confidentiality. To ensure its protection:
+
+1. **Limited Access**: Only authorized personnel within our technical support and development teams have access to the logs and debug logs containing sensitive data, and they are trained in handling this information securely.
+
+2. **Data Encryption**: We use industry-standard encryption protocols to protect the transmission and storage of sensitive data.
+
+3. **Data Retention**: We retain bug report data for a limited time necessary for resolving the reported issue. Once the issue is resolved, we promptly delete or anonymize the data.
+
+4. **Security Measures**: We employ robust security measures to prevent unauthorized access, disclosure, or alteration of sensitive data.
+
+By submitting a bug report, you acknowledge and consent to the inclusion of sensitive information in logs and debug logs for the sole purpose of addressing technical issues with the Software.
+
+## Your Responsibilities
+
+While we take measures to protect your sensitive data, it is essential for you to exercise caution when submitting bug reports. Please refrain from including any sensitive or personally identifiable information that is not directly related to the technical issue you are reporting. You have the option to redact or obfuscate sensitive details in bug reports to further protect your data.
+
+## Changes to this Privacy Policy
+
+We may update this Privacy Policy from time to time to reflect changes in our practices or for other operational, legal, or regulatory reasons. We will notify you of any material changes by posting the updated Privacy Policy on our website or through the Software. We encourage you to review this Privacy Policy periodically.
+
+## Contact Us
+
+If you have any questions or concerns about this Privacy Policy or our privacy practices, please contact us at support@mynas.com.au or via GitHub (https://github.com/abraunegg/onedrive)
+
+## Conclusion
+
+By using the Software, you agree to the terms outlined in this Privacy Policy. If you do not agree with any part of this policy, please discontinue the use of the Software.
+
--- a/docs/terms-of-service.md
+++ b/docs/terms-of-service.md
@ -0,0 +1,54 @@
+# OneDrive Client for Linux - Software Service Terms of Service
+
+## 1. Introduction
+
+These Terms of Service ("Terms") govern your use of the OneDrive Client for Linux ("Application") software and related Microsoft OneDrive services ("Service") provided by Microsoft. By accessing or using the Service, you agree to comply with and be bound by these Terms. If you do not agree to these Terms, please do not use the Service.
+
+## 2. License Compliance
+
+The OneDrive Client for Linux software is licensed under the GNU General Public License, version 3.0 (the "GPLv3"). Your use of the software must comply with the terms and conditions of the GPLv3. A copy of the GPLv3 can be found here: https://www.gnu.org/licenses/gpl-3.0.en.html
+
+## 3. Use of the Service
+
+### 3.1. Access and Accounts
+
+You may need to create an account or provide personal information to access certain features of the Service. You are responsible for maintaining the confidentiality of your account information and are solely responsible for all activities that occur under your account.
+
+### 3.2. Prohibited Activities
+
+You agree not to:
+
+- Use the Service in any way that violates applicable laws or regulations.
+- Use the Service to engage in any unlawful, harmful, or fraudulent activity.
+- Use the Service in any manner that disrupts, damages, or impairs the Service.
+
+## 4. Intellectual Property
+
+The OneDrive Client for Linux software is subject to the GPLv3, and you must respect all copyrights, trademarks, and other intellectual property rights associated with the software. Any contributions you make to the software must also comply with the GPLv3.
+
+## 5. Disclaimer of Warranties
+
+The OneDrive Client for Linux software is provided "as is" without any warranties, either expressed or implied. We do not guarantee that the use of the Application will be error-free or uninterrupted.
+
+Microsoft is not responsible for OneDrive Client for Linux. Any issues or problems with OneDrive Client for Linux should be raised on GitHub at https://github.com/abraunegg/onedrive or email support@mynas.com.au
+
+OneDrive Client for Linux is not responsible for the Microsoft OneDrive Service or the Microsoft Graph API Service that this Application utilizes. Any issue with either Microsoft OneDrive or Microsoft Graph API should be raised with Microsoft via their support channel in your country.
+
+## 6. Limitation of Liability
+
+To the fullest extent permitted by law, we shall not be liable for any direct, indirect, incidental, special, consequential, or punitive damages, or any loss of profits or revenues, whether incurred directly or indirectly, or any loss of data, use, goodwill, or other intangible losses, resulting from (a) your use or inability to use the Service, or (b) any other matter relating to the Service.
+
+This limitiation of liability explicitly relates to the use of the OneDrive Client for Linux software and does not affect your rights under the GPLv3.
+
+## 7. Changes to Terms
+
+We reserve the right to update or modify these Terms at any time without prior notice. Any changes will be effective immediately upon posting on GitHub. Your continued use of the Service after the posting of changes constitutes your acceptance of such changes. Changes can be reviewed on GitHub.
+
+## 8. Governing Law
+
+These Terms shall be governed by and construed in accordance with the laws of Australia, without regard to its conflict of law principles.
+
+## 9. Contact Us
+
+If you have any questions or concerns about these Terms, please contact us at https://github.com/abraunegg/onedrive or email support@mynas.com.au
+
--- a/docs/ubuntu-package-install.md
+++ b/docs/ubuntu-package-install.md
@ -135,18 +135,23 @@ If required, review the table below based on your 'lsb_release' information to p
 | Linux Mint 19.x           | This platform is End-of-Life (EOL) and no longer supported. You must upgrade to Linux Mint 21.x |
 | Linux Mint 20.x           | Use [Ubuntu 20.04](#distribution-ubuntu-2004) instructions below |
 | Linux Mint 21.x           | Use [Ubuntu 22.04](#distribution-ubuntu-2204) instructions below |
-| Debian 9                  | This platform is End-of-Life (EOL) and no longer supported. You must upgrade to Debian 11 |
-| Debian 10                 | You must build from source or upgrade your Operating System to Debian 11 |
+| Linux Mint Debian Edition (LMDE) 5 / Elsie | Use [Debian 11](#distribution-debian-11) instructions below |
+| Linux Mint Debian Edition (LMDE) 6 / Faye  | Use [Debian 12](#distribution-debian-12) instructions below |
+| Debian 9                  | This platform is End-of-Life (EOL) and no longer supported. You must upgrade to Debian 12 |
+| Debian 10                 | You must build from source or upgrade your Operating System to Debian 12 |
 | Debian 11                 | Use [Debian 11](#distribution-debian-11) instructions below |
-| Raspbian GNU/Linux 10     | You must build from source or upgrade your Operating System to Raspbian GNU/Linux 11 |
+| Debian 12                 | Use [Debian 12](#distribution-debian-12) instructions below |
+| Raspbian GNU/Linux 10     | You must build from source or upgrade your Operating System to Raspbian GNU/Linux 12 |
 | Raspbian GNU/Linux 11     | Use [Debian 11](#distribution-debian-11) instructions below |
-| Ubuntu 18.04 / Bionic     | This platform is End-of-Life (EOL) and no longer supported. You must upgrade to Ubuntu 22.x |
+| Raspbian GNU/Linux 12     | Use [Debian 12](#distribution-debian-12) instructions below |
+| Ubuntu 18.04 / Bionic     | This platform is End-of-Life (EOL) and no longer supported. You must upgrade to Ubuntu 22.04 |
 | Ubuntu 20.04 / Focal      | Use [Ubuntu 20.04](#distribution-ubuntu-2004) instructions below |
 | Ubuntu 21.04 / Hirsute    | Use [Ubuntu 21.04](#distribution-ubuntu-2104) instructions below |
 | Ubuntu 21.10 / Impish     | Use [Ubuntu 21.10](#distribution-ubuntu-2110) instructions below |
 | Ubuntu 22.04 / Jammy      | Use [Ubuntu 22.04](#distribution-ubuntu-2204) instructions below |
 | Ubuntu 22.10 / Kinetic    | Use [Ubuntu 22.10](#distribution-ubuntu-2210) instructions below |
 | Ubuntu 23.04 / Lunar      | Use [Ubuntu 23.04](#distribution-ubuntu-2304) instructions below |
+| Ubuntu 23.10 / Mantic     | Use [Ubuntu 23.10](#distribution-ubuntu-2310) instructions below |

 ## Distribution Package Install Instructions

@ -154,7 +159,7 @@ If required, review the table below based on your 'lsb_release' information to p
 The packages support the following platform architectures:
 | &nbsp;i686&nbsp; | x86_64 | ARMHF | AARCH64 |
 |:----:|:------:|:-----:|:-------:|
-|✔|✔|✔|✔| |
+|✔|✔|✔|✔|

 #### Step 1: Add the OpenSuSE Build Service repository release key
 Add the OpenSuSE Build Service repository release key using the following command:
@ -177,11 +182,38 @@ Run: `sudo apt install --no-install-recommends --no-install-suggests onedrive`
 #### Step 5: Read 'Known Issues' with these packages
 Read and understand the [known issues](#known-issues-with-installing-from-the-above-packages) with these packages below, taking any action that is needed.

+### Distribution: Debian 12
+The packages support the following platform architectures:
+| &nbsp;i686&nbsp; | x86_64 | ARMHF | AARCH64 |
+|:----:|:------:|:-----:|:-------:|
+|✔|✔|✔|✔|
+
+#### Step 1: Add the OpenSuSE Build Service repository release key
+Add the OpenSuSE Build Service repository release key using the following command:
+```text
+wget -qO - https://download.opensuse.org/repositories/home:/npreining:/debian-ubuntu-onedrive/Debian_12/Release.key | gpg --dearmor | sudo tee /usr/share/keyrings/obs-onedrive.gpg > /dev/null
+```
+
+#### Step 2: Add the OpenSuSE Build Service repository
+Add the OpenSuSE Build Service repository using the following command:
+```text
+echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/obs-onedrive.gpg] https://download.opensuse.org/repositories/home:/npreining:/debian-ubuntu-onedrive/Debian_12/ ./" | sudo tee /etc/apt/sources.list.d/onedrive.list
+```
+
+#### Step 3: Update your apt package cache
+Run: `sudo apt-get update`
+
+#### Step 4: Install 'onedrive'
+Run: `sudo apt install --no-install-recommends --no-install-suggests onedrive`
+
+#### Step 5: Read 'Known Issues' with these packages
+Read and understand the [known issues](#known-issues-with-installing-from-the-above-packages) with these packages below, taking any action that is needed.
+
 ### Distribution: Ubuntu 20.04
 The packages support the following platform architectures:
 | &nbsp;i686&nbsp; | x86_64 | ARMHF | AARCH64 |
 |:----:|:------:|:-----:|:-------:|
-❌|✔|✔|✔| |
+|❌|✔|✔|✔|

 #### Step 1: Add the OpenSuSE Build Service repository release key
 Add the OpenSuSE Build Service repository release key using the following command:
@ -208,7 +240,7 @@ Read and understand the [known issues](#known-issues-with-installing-from-the-ab
 The packages support the following platform architectures:
 | &nbsp;i686&nbsp; | x86_64 | ARMHF | AARCH64 |
 |:----:|:------:|:-----:|:-------:|
-❌|✔|✔|✔| |
+|❌|✔|✔|✔|

 #### Step 1: Add the OpenSuSE Build Service repository release key
 Add the OpenSuSE Build Service repository release key using the following command:
@ -235,7 +267,7 @@ Read and understand the [known issues](#known-issues-with-installing-from-the-ab
 The packages support the following platform architectures:
 | &nbsp;i686&nbsp; | x86_64 | ARMHF | AARCH64 |
 |:----:|:------:|:-----:|:-------:|
-❌|✔|✔|✔| |
+|❌|✔|✔|✔|

 #### Step 1: Add the OpenSuSE Build Service repository release key
 Add the OpenSuSE Build Service repository release key using the following command:
@ -262,7 +294,7 @@ Read and understand the [known issues](#known-issues-with-installing-from-the-ab
 The packages support the following platform architectures:
 | &nbsp;i686&nbsp; | x86_64 | ARMHF | AARCH64 |
 |:----:|:------:|:-----:|:-------:|
-❌|✔|✔|✔| |
+|❌|✔|✔|✔|

 #### Step 1: Add the OpenSuSE Build Service repository release key
 Add the OpenSuSE Build Service repository release key using the following command:
@ -289,7 +321,7 @@ Read and understand the [known issues](#known-issues-with-installing-from-the-ab
 The packages support the following platform architectures:
 | &nbsp;i686&nbsp; | x86_64 | ARMHF | AARCH64 |
 |:----:|:------:|:-----:|:-------:|
-❌|✔|✔|✔| |
+|❌|✔|✔|✔|

 #### Step 1: Add the OpenSuSE Build Service repository release key
 Add the OpenSuSE Build Service repository release key using the following command:
@ -316,7 +348,7 @@ Read and understand the [known issues](#known-issues-with-installing-from-the-ab
 The packages support the following platform architectures:
 | &nbsp;i686&nbsp; | x86_64 | ARMHF | AARCH64 |
 |:----:|:------:|:-----:|:-------:|
-❌|✔|✔|✔| |
+|❌|✔|✔|✔|

 #### Step 1: Add the OpenSuSE Build Service repository release key
 Add the OpenSuSE Build Service repository release key using the following command:
@ -339,6 +371,34 @@ Run: `sudo apt install --no-install-recommends --no-install-suggests onedrive`
 #### Step 5: Read 'Known Issues' with these packages
 Read and understand the [known issues](#known-issues-with-installing-from-the-above-packages) with these packages below, taking any action that is needed.

+### Distribution: Ubuntu 23.10
+The packages support the following platform architectures:
+| &nbsp;i686&nbsp; | x86_64 | ARMHF | AARCH64 |
+|:----:|:------:|:-----:|:-------:|
+|❌|✔|❌|✔|
+
+#### Step 1: Add the OpenSuSE Build Service repository release key
+Add the OpenSuSE Build Service repository release key using the following command:
+```text
+wget -qO - https://download.opensuse.org/repositories/home:/npreining:/debian-ubuntu-onedrive/xUbuntu_23.10/Release.key | gpg --dearmor | sudo tee /usr/share/keyrings/obs-onedrive.gpg > /dev/null
+```
+
+#### Step 2: Add the OpenSuSE Build Service repository
+Add the OpenSuSE Build Service repository using the following command:
+```text
+echo "deb [arch=$(dpkg --print-architecture) signed-by=/usr/share/keyrings/obs-onedrive.gpg] https://download.opensuse.org/repositories/home:/npreining:/debian-ubuntu-onedrive/xUbuntu_23.10/ ./" | sudo tee /etc/apt/sources.list.d/onedrive.list
+```
+
+#### Step 3: Update your apt package cache
+Run: `sudo apt-get update`
+
+#### Step 4: Install 'onedrive'
+Run: `sudo apt install --no-install-recommends --no-install-suggests onedrive`
+
+#### Step 5: Read 'Known Issues' with these packages
+Read and understand the [known issues](#known-issues-with-installing-from-the-above-packages) with these packages below, taking any action that is needed.
+
+
 ## Known Issues with Installing from the above packages

 ### 1. The client may segfault | core-dump when exiting
--- a/src/onedrive.d
+++ b/src/onedrive.d
@ -586,9 +586,19 @@ final class OneDriveApi
 			string[] authFiles = authFilesString.split(":");
 			string authUrl = authFiles[0];
 			string responseUrl = authFiles[1];
-			auto authUrlFile = File(authUrl, "w");
-			authUrlFile.write(url);
-			authUrlFile.close();
+			
+			try {
+				// Try and write out the auth URL to the nominated file
+				auto authUrlFile = File(authUrl, "w");
+				authUrlFile.write(url);
+				authUrlFile.close();
+			} catch (std.exception.ErrnoException e) {
+				// There was a file system error
+				// display the error message
+				displayFileSystemErrorMessage(e.msg, getFunctionName!({}));
+				return false;
+			}
+			
 			while (!exists(responseUrl)) {
 				Thread.sleep(dur!("msecs")(100));
 			}
--- a/src/sync.d
+++ b/src/sync.d
@ -2998,13 +2998,13 @@ final class SyncEngine
 		}
 		
 		if (!dryRun) {
-			ulong fileSize = 0;
+			ulong onlineFileSize = 0;
 			string OneDriveFileHash;
 			
 			// fileDetails should be a valid JSON due to prior check
 			if (hasFileSize(fileDetails)) {
-				// Use the configured filesize as reported by OneDrive
-				fileSize = fileDetails["size"].integer;
+				// Use the configured onlineFileSize as reported by OneDrive
+				onlineFileSize = fileDetails["size"].integer;
 			} else {
 				// filesize missing
 				log.vdebug("WARNING: fileDetails['size'] is missing");
@ -3018,12 +3018,13 @@ final class SyncEngine
 					if (fileDetails["file"]["hashes"]["quickXorHash"].str != "") {
 						OneDriveFileHash = fileDetails["file"]["hashes"]["quickXorHash"].str;
 					}
-				} 
-				// Check for sha256Hash
-				if (hasSHA256Hash(fileDetails)) {
-					// Use the configured sha256Hash as reported by OneDrive
-					if (fileDetails["file"]["hashes"]["sha256Hash"].str != "") {
-						OneDriveFileHash = fileDetails["file"]["hashes"]["sha256Hash"].str;
+				} else {
+					// Check for sha256Hash as quickXorHash did not exist
+					if (hasSHA256Hash(fileDetails)) {
+						// Use the configured sha256Hash as reported by OneDrive
+						if (fileDetails["file"]["hashes"]["sha256Hash"].str != "") {
+							OneDriveFileHash = fileDetails["file"]["hashes"]["sha256Hash"].str;
+						}
 					}
 				}
 			} else {
@ -3040,12 +3041,12 @@ final class SyncEngine
 			// debug output
 			log.vdebug("Local Disk Space Actual: ", localActualFreeSpace);
 			log.vdebug("Free Space Reservation:  ", freeSpaceReservation);
-			log.vdebug("File Size to Download:   ", fileSize);
+			log.vdebug("File Size to Download:   ", onlineFileSize);
 			
 			// calculate if we can download file
-			if ((localActualFreeSpace < freeSpaceReservation) || (fileSize > localActualFreeSpace)) {
+			if ((localActualFreeSpace < freeSpaceReservation) || (onlineFileSize > localActualFreeSpace)) {
 				// localActualFreeSpace is less than freeSpaceReservation .. insufficient free space
-				// fileSize is greater than localActualFreeSpace .. insufficient free space
+				// onlineFileSize is greater than localActualFreeSpace .. insufficient free space
 				writeln("failed!");
 				log.log("Insufficient local disk space to download file");
 				downloadFailed = true;
@ -3054,9 +3055,9 @@ final class SyncEngine
 			
 			// Attempt to download the file
 			try {
-				onedrive.downloadById(item.driveId, item.id, path, fileSize);
+				onedrive.downloadById(item.driveId, item.id, path, onlineFileSize);
 			} catch (OneDriveException e) {
-				log.vdebug("onedrive.downloadById(item.driveId, item.id, path, fileSize); generated a OneDriveException");
+				log.vdebug("onedrive.downloadById(item.driveId, item.id, path, onlineFileSize); generated a OneDriveException");
 				// 408 = Request Time Out 
 				// 429 = Too Many Requests - need to delay
 				if (e.httpStatusCode == 408) {
@ -3070,11 +3071,11 @@ final class SyncEngine
 						// retry in 2,4,8,16,32,64,128,256,512,1024 seconds
 						Thread.sleep(dur!"seconds"(retryAttempts*backoffInterval));
 						try {
-							onedrive.downloadById(item.driveId, item.id, path, fileSize);
+							onedrive.downloadById(item.driveId, item.id, path, onlineFileSize);
 							// successful download
 							retryAttempts = retryCount;
 						} catch (OneDriveException e) {
-							log.vdebug("onedrive.downloadById(item.driveId, item.id, path, fileSize); generated a OneDriveException");
+							log.vdebug("onedrive.downloadById(item.driveId, item.id, path, onlineFileSize); generated a OneDriveException");
 							if ((e.httpStatusCode == 429) || (e.httpStatusCode == 408)) {
 								// If another 408 .. 
 								if (e.httpStatusCode == 408) {
@ -3105,11 +3106,11 @@ final class SyncEngine
 						// retry after waiting the timeout value from the 429 HTTP response header Retry-After
 						handleOneDriveThrottleRequest();
 						try {
-							onedrive.downloadById(item.driveId, item.id, path, fileSize);
+							onedrive.downloadById(item.driveId, item.id, path, onlineFileSize);
 							// successful download
 							retryAttempts = retryCount;
 						} catch (OneDriveException e) {
-							log.vdebug("onedrive.downloadById(item.driveId, item.id, path, fileSize); generated a OneDriveException");
+							log.vdebug("onedrive.downloadById(item.driveId, item.id, path, onlineFileSize); generated a OneDriveException");
 							if ((e.httpStatusCode == 429) || (e.httpStatusCode == 408)) {
 								// If another 408 .. 
 								if (e.httpStatusCode == 408) {
@ -3150,11 +3151,13 @@ final class SyncEngine
 				// we have implemented --disable-download-validation to disable these checks
 				
 				if (!disableDownloadValidation) {
-					// A 'file' was downloaded - does what we downloaded = reported fileSize or if there is some sort of funky local disk compression going on
+					// A 'file' was downloaded - does what we downloaded = reported onlineFileSize or if there is some sort of funky local disk compression going on
 					// does the file hash OneDrive reports match what we have locally?
 					string quickXorHash = computeQuickXorHash(path);
+					// Compute the local file size
+					ulong localFileSize = getSize(path);
 					
-					if ((getSize(path) == fileSize) || (OneDriveFileHash == quickXorHash)) {
+					if ((localFileSize == onlineFileSize) || (OneDriveFileHash == quickXorHash)) {
 						// downloaded matches either size or hash
 						log.vdebug("Downloaded file matches reported size and or reported file hash");
 						try {
@ -3166,17 +3169,17 @@ final class SyncEngine
 						}
 					} else {
 						// size error?
-						if (getSize(path) != fileSize) {
+						if (localFileSize != onlineFileSize) {
 							// downloaded file size does not match
-							log.vdebug("File size on disk:          ", getSize(path));
-							log.vdebug("OneDrive API reported size: ", fileSize);
+							log.vdebug("Actual file size on disk:   ", localFileSize);
+							log.vdebug("OneDrive API reported size: ", onlineFileSize);
 							log.error("ERROR: File download size mis-match. Increase logging verbosity to determine why.");
 						}
 						// hash error?
 						if (OneDriveFileHash != quickXorHash) {
 							// downloaded file hash does not match
-							log.vdebug("Actual file hash:           ", OneDriveFileHash);
-							log.vdebug("OneDrive API reported hash: ", quickXorHash);
+							log.vdebug("Actual local file hash:     ", quickXorHash);
+							log.vdebug("OneDrive API reported hash: ", OneDriveFileHash);
 							log.error("ERROR: File download hash mis-match. Increase logging verbosity to determine why.");
 						}
 						// add some workaround messaging
Author	SHA1	Message	Date
abraunegg	1a88d33be3	Backport v2.5.x documentation changes * Backport v2.5.x documentation changes for Docker and Podman	2023-11-16 09:15:30 +11:00
abraunegg	6282ec9e3b	Update ubuntu-package-install.md * Update doc to align to v2.5.x version	2023-11-10 04:50:50 +11:00
abraunegg	4a60654e3f	Update USAGE.md * Fix documentation regarding skip_file example	2023-09-25 08:04:29 +10:00
abraunegg	a74ff589f8	Update USAGE.md (#2488 ) * Add classify_as_big_delete	2023-09-14 07:06:56 +10:00
abraunegg	651aa16844	Update application-security.md * Fix spelling error	2023-09-11 10:16:50 +10:00
abraunegg	85f99cb899	Update Security Documents (#2484 ) * Update Security Documents	2023-09-11 07:26:14 +10:00
abraunegg	d712dd6093	Update USAGE.md * Add note about minimum value for ''monitor_interval'	2023-08-31 09:55:54 +10:00
abraunegg	43b0bed4cb	Fix debugging log output when reporting file size and hash mismatch (#2473 ) * Fix debug logging output with correct hash values as these were switched * Only calculate local file size post download once and reuse value	2023-08-24 18:08:21 +10:00
Flynn Duniho	fc5cbaf2e9	Fix typo in USAGE.md (#2466 ) * Fix typo in USAGE.md	2023-08-07 12:44:40 +10:00
abraunegg	50d80d333e	Add Debian 12 to documentation (#2459 ) * Add Debian 12 to documentation	2023-07-27 05:32:20 +10:00
Gonçalo Martins	99271a45de	Add --no-remote-delete flag to docker entrypoint (#2453 ) * Add --no-remote-delete flag to docker entrypoint --------- Co-authored-by: Gonçalo Martins <g.martins@revolut.com> Co-authored-by: abraunegg <alex.braunegg@gmail.com>	2023-07-24 10:41:06 +10:00
abraunegg	fb0a5f0796	Fix unhandled exception when authurl path is non-existent (#2456 ) * Catch an unhandled exception when the user sets the authurl file to a location that cannot be accessed	2023-07-23 10:13:03 +10:00
abraunegg	94ccb7a6d0	Update webhook example configuration documentation * Update webhook example configuration based on #2447	2023-07-11 18:09:45 +02:00