

- BACKBLAZE SYNOLOGY PERSONAL INSTALL
- BACKBLAZE SYNOLOGY PERSONAL FULL
- BACKBLAZE SYNOLOGY PERSONAL WINDOWS
When mounting docker-volumes, permission issues can arise between the docker host and the container. You can pass the User_ID permissions to the container with this variable. In this case, the container should be run with the docker option -cap-add=SYS_NICE. NOTE: A negative niceness (priority increase) requires additional permissions. By default, niceness is not set, meaning that the default niceness of 0 is used. A niceness value of -20 is the highest priority and 19 is the lowest priority. Priority at which the application should run. Timezone can also be set by mapping /etc/localtime between the host and the container. See the following online umask calculator: By default, this variable is not set and the default umask of 022 is used, meaning that newly created files are readable by everyone, but only writable by the owner. The value of the mask is in octal notation. Mask that controls how file permissions are set for newly created files. Environment VariablesĮnvironment variables can be set by adding one or more arguments -e "=" to the docker run command.
BACKBLAZE SYNOLOGY PERSONAL WINDOWS
Platforms PlatformĬurrently no support (maybe in the future)Īs Backblaze runs on Windows and MacOS, there is no point in supporting these platforms. There are currently no versioned ubuntu18 builds.

Versioned stable releases based on ubuntu 20Īutomatic build of the main branch (may be unstable) based on ubuntu 20 Latest stable version of the image based on ubuntu 18 Latest stable version of the image based on ubuntu 20
BACKBLAZE SYNOLOGY PERSONAL INSTALL

BACKBLAZE SYNOLOGY PERSONAL FULL
bzvol directory in the root of every hard drive it's configured to back up in which it'll store a full copy of files >100M split into 10M parts. The -init flag installs a tiny process that can actually do a few init things like wait()ing children in place of the backblaze client as PID 1. This will cause it to fill up your system's PID limit within a few hours which prevents new processes from being created system-wide, would not recommend. Warning: The backblaze client is not an init system (who knew) and doesn't clean up its zombie children. I have my WINE prefix set up in a way that dosdrives/d: is a symlink to drive_d and told backblaze to back up "D:\" and ignore everything on "C:\".
