appdefs.yml

---

#
# Definitions for CrashPlan PRO docker container.
#
# This file is used as data source to generate README.md and unRAID template files
# from Jinja2 templates.
#

app:
  id: 10
  name: crashplan-pro
  friendly_name: CrashPlan
  gui_type: x11
  base_os: alpine
  project:
    description: |-
      CrashPlan provides peace of mind through secure, scalable, and
      straightforward endpoint data backup. We help organizations recover from
      any worst-case scenario, whether it is a disaster, simple human error, a
      stolen laptop, ransomware or an as-of-yet undiscovered calamity.
    url: https://www.crashplan.com
  unraid:
    name: CrashPlanPRO
    extra_description: >-
      **Warning**: Make sure to read the *Taking Over Existing Backup* section of the
      documentation if you are installing this container to replace another CrashPlan
      installation (from Windows, Linux, Mac or even another Docker container).
    support_url: https://forums.unraid.net/topic/59647-support-crashplan-pro/
    category: "Backup:"
  documentation:
    overview: |-
      This Docker container can be used with all CrashPlan products: Essential,
      Professional, Enterprise, MSPs and Small Business (no longer sold).
    sections:
      - title: Taking Over Existing Backup
        level: 2
        content: |-
          If this container is replacing a CrashPlan installation (from Linux, Windows,
          MAC or another Docker container), your existing backup can be taken over to
          avoid re-uploading all your data.

          To proceed, make sure to carefully read the [official documentation].

          Here is a summary of what needs to be done:
            1. Start CrashPlan Docker container.  Make sure the configuration directory
               is not mapped to a folder used by a different CrashPlan container.
            2. Sign in to your account.
            3. Click the **Replace Existing** button to start the wizard.
            4. Skip *Step 2 - File Transfer*.
            4. Once done with the wizard, go to your device's details and click
               *Manage Files*.  You will probably see missing items in the file
               selection.  This is normal, since path to your files may be different in
               the container.
            5. Update the file selection by re-adding your files.  **Do not unselect
               missing items yet**.
            6. Perform a backup.  Because of deduplication, files will not be uploaded
               again.
            7. Once the backup is terminated, you can remove missing items **if you
               don't care about file versions**.  Else, keep missing items.

          **NOTE**: Don't be confused by the directory structure from your old being
          visible in the *Manage Files* window.  By default, your files are now located
          under the `/storage` folder.

          [official documentation]: https://support.code42.com/hc/en-us/articles/14827668736279-Replace-your-device
      - title: Why CrashPlan Self Update Is Disabled
        level: 2
        content: |-
          One advantage of a Docker image is that it can be versioned and predictable,
          meaning that a specific version of the image always behaves the same way.  So
          if, for any reason, a new image version has a problem and doesn't work as
          expected, it's easy for one to revert to the previous version and be back on
          track.

          Allowing CrashPlan to update itself obviously breaks this benefit.  Also, since
          the container has only the minimal set of libraries and tools required to run
          CrashPlan, it would be easy for an automatic update to break the container by
          requiring new dependencies.  Finally, the automatic update script is not adapted
          for Alpine Linux (the distribution on which this container is based on) and
          assumes it is running on a full-featured distribution.  For example, this image
          doesn't have a desktop like normal installations and some of the tools required
          to perform the update are missing.
      - title: Troubleshooting
        level: 2
      - title: Crashes / Maximum Amount of Allocated Memory
        level: 3
        content: |-
          If CrashPlan crashes unexpectedly with large backups, try to increase the
          maximum amount of memory CrashPlan is allowed to use. This can be done by:

            1. Setting the `CRASHPLAN_SRV_MAX_MEM` environment variable.  See the
               [Environment Variables](#environment-variables) section for more details.
            2. Using the [solution provided by CrashPlan] from its support site.

          [solution provided by CrashPlan]: https://support.code42.com/hc/en-us/articles/14827635282583-Adjust-Code42-agent-settings-for-memory-usage-with-large-backups
      - title: Inotify's Watch Limit
        level: 3
        content: |-
          If CrashPlan exceeds inotify's max watch limit, real-time file watching cannot
          work properly and the inotify watch limit needs to be increased on the **host**,
          not the container.

          For more details, see the CrashPlan's [Linux real-time file watching errors]
          article.

          [Linux real-time file watching errors]: https://support.code42.com/hc/en-us/articles/14827708807959-Linux-real-time-file-watching-errors
      - title: Synology
        level: 4
        content: |-
          On Synology NAS, the instructions provided by the article mentioned in the
          previous section apply, except that the inotify's max watch limit must be set in
          `/etc.defaults/sysctl.conf` (instead of `/etc/sysctl.conf`) to make the setting
          permanent.

          **NOTE**: After an upgrade of the DSM software, verify that the content of the
          file has not been overwritten.
      - title: Empty `/storage`
        level: 3
        content: |-
          If the `/storage` folder inside the container is empty:

            - Make sure the folder is properly mapped to the host.  This is done via the
              `-v` parameter of the `docker run` command.  See the [Usage](#usage)
              section.
            - Make sure permissions and ownership of files on the host are correct and are
              compatible with the user under which the container application is running
              (defined by the `USER_ID` and `GROUP_ID` environment variables).  See the
              [User/Group IDs](#usergroup-ids) section.

          NOTE: If running the application as root (`USER_ID=0` and `GROUP_ID=0`) makes
          the files visible, it confirms that there is a permission issue.
      - title: Device Status Is Waiting For Connection
        level: 3
        content: |-
          If the status of your device is stuck on *Waiting for connection*, clearing the
          the cache of CrashPlan can help resolve the issue:

            - Stop the container.
            - Remove all the content of the `cache` directory found under the container's
              configuration directory.  For example, if the `/config` folder of the
              container is mapped to `/docker/appdata/crashplan-pro` on the host, the
              following command (ran on the host) would clear the cache:
              ```
              rm -rf /docker/appdata/crashplan-pro/cache/*
              ```
            - Start the container.
      - title: Cannot Restore Files
        level: 3
        content: |-
          If CrashPlan fails to restore files, make sure the location where files are
          restored have write permission.

          A typical installation has the data to be backup under the `/storage` folder.
          This folder is usually mapped to the host with *read-only* permission.  Thus,
          restoring files to `/storage` won't be allowed.  The solution is to temporarily
          change the permission of the volume to *read-write*.

          For example, if `/storage` is mapped to `/home/user` on the host, the container
          would need to be deleted and then re-created with the same arguments, with the
          exception of `-v /home/user:/storage:ro` that is replaced with
          `-v /home/user:/storage:rw`.
      - title: Upgrade Failed Error Message
        level: 3
        content: |-
          Because the CrashPlan's self-upgrade feature is disabled in this container, an
          error message about failed upgrade can be seen when a new CrashPlan version is
          released.

          To fix this, [updating the container's image](#docker-image-update) to the
          latest version will also bring the latest version of CrashPlan.
  changelog:
    - version: 24.12.1
      date: 2024-12-07
      changes:
        - 'Updated baseimage to version 4.6.7, which brings the following changes:'
        - '2:Fixed web audio feature with URL path-based reverse proxy.'
        - '2:Fixed TLS secure connection method for VNC that was preventing web access.'
        - '2:Fixed CJK font installation.'
        - '2:Rebuild against latest distro images to get security fixes.'
    - version: 24.11.1
      date: 2024-11-18
      changes:
        - 'Updated CrashPlan to version 11.5.0.'
    - version: 24.10.1
      date: 2024-10-14
      changes:
        - 'Updated CrashPlan to version 11.4.1.'
        - 'Updated baseimage to version 4.6.4, which brings the following changes:'
        - '2:Fixed web authentication feature with URL path-based reverse proxy.'
        - '2:Rebuild against latest distro images to get security fixes.'
    - version: 24.08.1
      date: 2024-08-01
      changes:
        - 'Updated CrashPlan to version 11.4.0.'
        - 'Updated baseimage to version 4.6.3, which brings the following changes:'
        - '2:Audio support through web browser.'
        - '2:Web authentication support.'
        - '2:Better support of GTK4 applications.'
        - '2:Updated noVNC to version 1.5.0.'
        - '2:Updated web UI components (Bootstrap, Font Awesome).'
        - '2:When connecting, the control bar is now temporarily shown only once.'
        - '2:During package mirror setup, make sure to keep permissions of copied files.'
    - version: 24.01.1
      date: 2024-01-12
      changes:
        - 'Updated CrashPlan to version 11.2.1.'
        - 'Updated baseimage to version 4.5.3, which brings the following changes:'
        - '2:Disabled fullscreen support when page is loaded into an iFrame.'
        - '2:Rebuilt against latest distro images to get security fixes.'
    - version: 23.12.1
      date: 2023-12-16
      changes:
        - 'Make sure the server used for the Small Business edition is configured, even when the container is not upgrading or running for the first time.'
    - version: 23.11.4
      date: 2023-11-28
      changes:
        - 'Added support for new CrashPlan products.'
        - 'The CrashPlan server address can be set via the `CRASHPLAN_SERVER_ADDRESS` environment variable.'
    - version: 23.11.3
      date: 2023-11-19
      changes:
        - 'Updated baseimage to version 4.5.2, which brings the following changes:'
        - '2:Fixed issue that would cause the helper that takes ownership of a directory to fail when using a very high user or group ID.'
    - version: 23.11.2
      date: 2023-11-10
      changes:
        - 'Updated baseimage to version 4.5.1, which brings the following changes:'
        - '2:Mirror for packages installation can be set via the `PACKAGES_MIRROR` environment variable.'
        - '2:Improved the way the `take-ownership` script is working.'
        - '2:Readiness and minimum running time checks should not be done for a service defined with an interval.'
        - '2:Raise an error when a synched service fails to start.'
        - '2:Minimum running time check of a service was using an incorrect way to verify if process is still alive.'
        - '2:Fixed installation of CJK font.'
    - version: 23.11.1
      date: 2023-11-07
      changes:
        - 'Updated CrashPlan to version 11.2.0.'
    - version: 23.06.2
      date: 2023-06-21
      changes:
        - 'Updated CrashPlan to version 11.1.1.'
    - version: 23.06.1
      date: 2023-06-07
      changes:
        - 'Updated baseimage to version 4.4.2, which brings the following changes:'
        - '2:Rebuilt against latest distro images to get security fixes.'
        - '2:Updated X server to version 1.20.14.'
    - version: 23.04.2
      date: 2023-04-29
      changes:
        - 'Updated baseimage to version 4.4.1, which brings the following changes:'
        - '2:Updated TigerVNC to version 1.13.1.'
    - version: 23.04.1
      date: 2023-04-13
      changes:
        - 'Updated CrashPlan to version 11.0.1.'
    - version: 23.03.1
      date: 2023-03-05
      changes:
        - 'Updated baseimage to version 4.4.0, which brings the following changes:'
        - '2:Updated components providing access to application''s UI over web.'
        - '2:Improved web UI usage with touch devices.'
        - '2:Fixed issue with initialization of Linux users and groups when the `GROUP_ID` is also part of `SUP_GROUP_IDS`.'
        - '2:Limit the maximum number of opened files on system having a very large, unlimited value. This prevents unnecessary waste of CPU resources and time for applications trying to close all possible file descriptors.'
    - version: 23.02.2
      date: 2023-02-08
      changes:
        - 'Updated baseimage to version 4.3.4, which brings the following changes:'
        - '2:Fixed error message from openbox about missing Fontconfig cache directory.'
        - 'Do not use the OCI Docker image format yet to keep better compatibility (e.g with older docker clients).'
    - version: 23.02.1
      date: 2023-02-04
      changes:
        - 'Updated baseimage to version 4.3.3, which brings robustness related enhancements.'
    - version: 23.01.1
      date: 2023-01-04
      changes:
        - 'Update of the baseimage to version 4.3.1 brings the following changes:'
        - '2:Control menu can be moved to the right side of the screen.'
        - '2:Automatic focus of the clipboard text box when opening the control menu.'
        - '2:Automatic close of the control menu when clicking into the application.'
        - '2:Rotation of the internal web server log files.'
    - version: 22.12.2
      date: 2022-12-11
      changes:
        - 'Implemented workaround for issue seen with Synology devices where container would not start after an image update.  The problem is caused by Synology explicitly setting all environment variables and keeping values from the old version.'
    - version: 22.12.1
      date: 2022-12-10
      changes:
        - 'Updated baseimage to version 4.2.1, which brings multiple internal enhancements.'
    - version: 22.11.3
      date: 2022-11-21
      changes:
        - 'Updated CrashPlan to version 10.4.1.'
    - version: 22.11.2
      date: 2022-11-07
      changes:
        - 'Fixed issue where the log monitor would use too much CPU.'
        - 'Fixed issue where the same alert would be shown multiple times.'
    - version: 22.11.1
      date: 2022-11-02
      changes:
        - 'Fixed display of non-english characters in filenames.'
    - version: 22.10.4
      date: 2022-10-30
      changes:
        - 'Fixed UI crash that was occuring when opening a file/directory selection window.'
    - version: 22.10.3
      date: 2022-10-30
      changes:
        - 'Fixed the history window being full screen.'
    - version: 22.10.2
      date: 2022-10-29
      changes:
        - 'Do not prevent the container from starting if CrashPlan engine is taking too long to start.'
    - version: 22.10.1
      date: 2022-10-29
      changes:
        - 'Updated CrashPlan to version 10.4.0.'
        - 'Versioning scheme of the Docker image changed to `YY.MM.SEQUENCE`.'
        - 'Update of the baseimage to version 4.1.2 brings the following new features:'
        - '2:Support for remote window resize.'
        - '2:Updated the web UI with a new, simplified and less intrusive look.'
    - version: 2.17.2
      date: 2022-08-06
      changes:
        - 'Updated CrashPlan to version 10.2.1.'
    - version: 2.17.1
      date: 2022-07-15
      changes:
        - 'Updated CrashPlan to version 10.2.0.'
    - version: 2.17.0
      date: 2022-05-15
      changes:
        - 'Updated CrashPlan to version 10.0.0.'
    - version: 2.16.8
      date: 2022-03-24
      changes:
        - 'Updated CrashPlan to version 8.8.4.'
    - version: 2.16.7
      date: 2022-02-25
      changes:
        - 'Updated CrashPlan to version 8.8.3.39.'
    - version: 2.16.6
      date: 2022-02-15
      changes:
        - 'Fixed an issue where restoring files would not work.'
        - 'Now using baseimage version 3.5.8, based on Alpine 3.14, which brings the following change:'
        - '2:Updated installed packages to get latest security fixes.'
    - version: 2.16.5
      date: 2022-01-21
      changes:
        - 'Updated CrashPlan to version 8.8.2.143.'
    - version: 2.16.4
      date: 2021-12-26
      changes:
        - 'Fixed, again, an issue where restoring files to an "other" location would crash the UI.'
    - version: 2.16.3
      date: 2021-12-25
      changes:
        - 'Added workaround for an issue where the CrashPlan engine would not start on devices running older kernel version.'
    - version: 2.16.2
      date: 2021-12-25
      changes:
        - 'Fixed an issue where restoring files to an "other" location would crash the UI.'
        - 'Fixed handling of filenames with special characters.'
    - version: 2.16.1
      date: 2021-12-20
      changes:
        - 'Updated CrashPlan to version 8.8.1.36.'
    - version: 2.16.0
      date: 2021-12-16
      changes:
        - 'Updated CrashPlan to version 8.8.1.'
    - version: 2.15.1
      date: 2021-09-08
      changes:
        - 'Updated CrashPlan to version 8.7.1.'
    - version: 2.15.0
      date: 2021-08-12
      changes:
        - 'Updated CrashPlan to version 8.7.0.'
    - version: 2.14.1
      date: 2021-06-03
      changes:
        - 'Updated CrashPlan to version 8.6.1.'
    - version: 2.14.0
      date: 2021-03-18
      changes:
        - 'Updated CrashPlan to version 8.6.0.'
    - version: 2.13.1
      date: 2020-10-29
      changes:
        - 'Removed debug messages that were left by mistake.'
    - version: 2.13.0
      date: 2020-10-20
      changes:
        - 'Updated CrashPlan PRO to version 8.5.0.'
    - version: 2.12.2
      date: 2020-09-10
      changes:
        - 'Fixed an issue that was preventing files to be restored.'
        - 'Fixed an issue where the restart command of the console would not work.'
    - version: 2.12.1
      date: 2020-08-05
      changes:
        - 'Upgraded CrashPlan PRO to version 8.2.2.'
        - 'Now using baseimage version 3.5.6, which brings the following changes:'
        - '2:Other small adjustments for the YAD log monitor target.'
    - version: 2.12.0
      date: 2020-07-19
      changes:
        - 'Upgraded CrashPlan PRO to version 8.2.0.'
        - 'Now using baseimage v3.5.5, which brings the following changes:'
        - '2:Upgraded glibc to version 2.31 on Alpine Linux images with glibc integrated.'
        - '2:Updated installed packages to get latest security fixes.'
        - '2:Adjusted the log monitor target for recent versions of YAD.'
    - version: 2.11.0
      date: 2020-05-10
      changes:
        - 'Upgraded CrashPlan PRO to version 8.0.0.'
    - version: 2.10.1
      date: 2020-04-06
      changes:
        - 'Fixed handling of CRASHPLAN_SRV_MAX_MEM.'
    - version: 2.10.0
      date: 2020-02-12
      changes:
        - 'Upgraded CrashPlan PRO to version 7.7.0.'
    - version: 2.9.0
      date: 2019-11-22
      changes:
        - 'Upgraded CrashPlan PRO to version 7.4.0.'
        - 'Now using baseimage v3.5.3, which brings the following changes:'
        - '2:Updated installed packages to get latest security fixes.'
        - '2:Make sure the tzdata is installed.'
    - version: 2.8.2
      date: 2019-10-22
      changes:
        - 'Fixed a notification message.'
    - version: 2.8.1
      date: 2019-10-08
      changes:
        - 'Fixed issue where the wrong log file was monitored.'
    - version: 2.8.0
      date: 2019-09-18
      changes:
        - 'Upgraded CrashPlan Enterprise to version 7.2.0.'
    - version: 2.7.3
      date: 2019-09-05
      changes:
        - 'Fixed misleading message about real-time file watching failure.'
    - version: 2.7.2
      date: 2019-07-13
      changes:
        - 'Upgraded CrashPlan PRO to version 7.0.0 build 585.'
    - version: 2.7.1
      date: 2019-06-22
      changes:
        - 'Fixed an issue where setting (via the environment variable) the maximum amount of memory CrashPlan is allowed to use would prevent the engine to start.'
    - version: 2.7.0
      date: 2019-06-22
      changes:
        - 'Upgraded CrashPlan PRO to version 7.0.0.'
    - version: 2.6.4
      date: 2019-04-24
      changes:
        - 'Now using baseimage v3.5.2, which brings the following changes:'
        - '2:Updated installed packages to get latest security fixes.'
        - '2:Fixed issue where the container could have a zombie process.'
        - '2:Fixed issue where the password would not be submitted when pressing the enter key in the password modal.'
        - '2:Use relative path for favicon ressources to be more friendly with reverse proxy senarios.'
    - version: 2.6.3
      date: 2019-04-20
      changes:
        - 'Upgraded CrashPlan PRO to version 6.9.4.'
    - version: 2.6.2
      date: 2019-02-20
      changes:
        - 'Upgraded CrashPlan PRO to version 6.9.2.'
    - version: 2.6.1
      date: 2018-12-19
      changes:
        - 'Upgraded to build 827 of CrashPlan PRO 6.9.0.'
        - 'Updated logo of Crashplan.'
    - version: 2.6.0
      date: 2018-12-09
      changes:
        - 'Upgraded CrashPlan PRO to version 6.9.0.'
        - 'Make sure only the numerical kernel version is reported to CrashPlan PRO.'
    - version: 2.5.0
      date: 2018-09-20
      changes:
        - 'Upgraded CrashPlan PRO to version 6.8.3.'
    - version: 2.4.1
      date: 2018-09-18
      changes:
        - 'Now using baseimage v3.5.1, which brings the following changes:'
        - '2:Updated installed packages to get latest security fixes.'
    - version: 2.4.0
      date: 2018-08-22
      changes:
        - 'Upgraded CrashPlan PRO to version 6.8.2.'
        - 'Now using baseimage v3.5.0, which brings the following changes (since last used version):'
        - '2:Based on Alpine Linux 3.8.'
        - '2:Upgraded s6-overlay to version 1.21.4.0.'
        - '2:Wait for a limited time when terminating a service.'
        - '2:Set and create the XDG_RUNTIME_DIR directory.'
    - version: 2.3.8
      date: 2018-08-10
      changes:
        - 'Fixed and issue where container would fail to start on host running CentOS.'
    - version: 2.3.7
      date: 2018-06-14
      changes:
        - 'To make sure the CrashPlan Engine will start, validate the value of CRASHPLAN_SRV_MAX_MEM variable during startup.'
    - version: 2.3.6
      date: 2018-06-11
      changes:
        - 'Fixed more instances where parsing of CrashPlan memory usage would fail.'
    - version: 2.3.5
      date: 2018-06-06
      changes:
        - 'Fixed an issue where parsing of CrashPlan memory usage would fail.'
    - version: 2.3.4
      date: 2018-05-15
      changes:
        - 'Upgraded CrashPlan to version 6.7.2.'
    - version: 2.3.3
      date: 2018-04-23
      changes:
        - 'Fixed issue where supplementary groups were not applied to the CrashPlan engine.'
    - version: 2.3.2
      date: 2018-04-03
      changes:
        - 'Upgraded CrashPlan to version 6.7.1.'
        - 'Fixed an issue where running the container as user `nobody` (id 65534) would fail.'
        - 'Switched to a baseimage based on Alpine Linux 3.7.'
    - version: 2.3.1
      date: 2018-03-05
      changes:
        - 'Use the correct variable to keep the application running.'
    - version: 2.3.0
      date: 2018-03-02
      changes:
        - 'Now using baseimage v3.3.4, which brings the following changes (since last used version):'
        - '2:Make sure the log monitor is started after the X server.'
        - '2:Fixed an issue where the log monitor `yad` target would use XDG folders of the application.'
        - '2:Fixed issue where log monitor states were not cleared during container startup.'
        - 'Trigger a notification when file restore fails due to `/storage` being read-only.'
    - version: 2.2.1
      date: 2018-02-03
      changes:
        - 'Now using baseimage v3.3.2, which brings the following changes:'
        - '2:Restored timezone support in Alpine Linux images with glibc.'
        - '2:Fixed issue in `add-pkg` helper where a package could be incorrectly detected as installed.'
    - version: 2.2.0
      date: 2018-02-02
      changes:
        - 'Updated CrashPlan PRO to version 6.7.0.'
    - version: 2.1.1
      date: 2018-01-30
      changes:
        - 'Now using baseimage v3.3.1, which brings the following changes:'
        - '2:Adjusted the way some ressources are accessed to better support reverse proxy to the container.'
    - version: 2.1.0
      date: 2018-01-22
      changes:
        - 'Now using baseimage v3.3.0, which brings the following changes (since last used version):'
        - '2:For Alpine Linux images with glibc, automatically update dynamic linker''s cache after new libraries are installed.'
        - '2:Fixed the LANG environment variable not being set properly.'
        - '2:Added the ability to automatically install a CJK (Chinese/Japanese/Korean) font.'
    - version: 2.0.4
      date: 2018-01-11
      changes:
        - 'Fixed issue where libraries were not found.'
    - version: 2.0.3
      date: 2018-01-11
      changes:
        - 'Now using baseimage v3.2.2, which brings the following changes (since last used version):'
        - '2:Upgraded S6 overlay to version 1.21.2.2.'
        - '2:Upgraded glibc to version 2.26 (Alpine Linux glibc images).'
        - '2:Adjusted the way ownership of /config is taken to better support cases where the folder is mapped to a network share.'
        - 'Small adjustment to the way ownership of files are taken.'
    - version: 2.0.2
      date: 2017-12-14
      changes:
        - 'Fixed an issue where the CrashPlan UI would not connect to the engine using the loopback IP.'
        - 'Fixed an issue where automatic update could be partially done when running the container as root.'
    - version: 2.0.1
      date: 2017-12-12
      changes:
        - 'Now using baseimage v3.1.4, which brings the following changes:'
        - '2:Set 2 worker processes for nginx.'
    - version: 2.0.0
      date: 2017-12-08
      changes:
        - 'Upgraded CrashPlan to version 6.6.0.'
    - version: 1.2.2
      date: 2017-11-20
      changes:
        - 'Now using baseimage v3.1.3, which brings the following changes:'
        - '2:Upgraded S6 overlay to version 1.21.2.1.'
    - version: 1.2.1
      date: 2017-11-07
      changes:
        - 'Now using baseimage v3.1.2, which brings the following changes (from last used version):'
        - '2:Fixed an issue where a self-disabled service could be restarted.'
        - '2:Upgraded S6 overlay to version 1.21.2.0.'
        - '2:Use a more efficient way to monitor status files.'
        - 'Wait for the CrashPlan engine to be ready before starting the UI.'
    - version: 1.2.0
      date: 2017-10-30
      changes:
        - 'Now using baseimage v3.1.0, which brings the following changes:'
        - '2:Upgraded S6 overlay to version 1.21.1.1.'
        - '2:Enhanced integration of service dependencies functionality.'
        - '2:Added a simple log monitor.'
        - '2:Fixed race condition where container''s exit code would not be the expected one.'
        - '2:Fixed issue where application''s GUI fails to displayed when accessing it through the web interface via standard ports 80/443.'
        - 'Alert user of common problems.'
    - version: 1.1.2
      date: 2017-10-09
      changes:
        - 'Now using baseimage v3.0.2, which brings the following changes:'
        - '2:Fixed issue where nginx config change was not applied correctly on systems without IPV6 support and secure connection disabled.'
    - version: 1.1.1
      date: 2017-10-08
      changes:
        - 'Now using baseimage v3.0.1, which brings the following changes:'
        - '2:Fixed nginx config for systems without IPV6 support.'
    - version: 1.1.0
      date: 2017-10-08
      changes:
        - 'Now using baseimage v3.0.0, which brings the following changes:'
        - '2:Better support for service dependencies.'
        - '2:Added support for secure access to the application''s GUI.'
    - version: 1.0.1
      date: 2017-09-08
      changes:
        - 'Now using baseimage v2.0.8, which brings the following changes (from last used version):'
        - '2:Fixed timezone support on alpine-glibc images.'
        - '2:Fixed duplicated entries in /etc/passwd and /etc/group that were created after a restart of the container.'
    - version: 1.0.0
      date: 2017-08-24
      changes:
        - 'Initial release.'

container:
  storage_permissions: ro

  # Environment variables.
  environment_variables:
    - name: CRASHPLAN_SRV_MAX_MEM
      description: >-
        Maximum amount of memory the CrashPlan Engine is allowed to use. One of
        the following memory unit (case insensitive) should be added as a suffix
        to the size: `G`, `M` or `K`.  By default, when this variable is not
        set, a maximum of 1024MB (`1024M`) of memory is allowed. **NOTE**:
        Setting this variable as the same effect as running the `java mx VALUE,
        restart` command from the CrashPlan command line.
      type: public
      default: 1024M
      unraid_template:
        title: Maximum Memory
        description: >-
          Maximum amount of memory the CrashPlan Engine is allowed to use.  One
          of the following memory unit (case insensitive) should be added as a
          suffix to the size: G, M or K.
        display: advanced
        required: false
        mask: false

  # Volumes
  volumes: []

  # Network ports
  ports: []

  # Devices
  devices: []