Skip to content

Docker BackupPC server w/ S6 overlay, Zabbix montioring support based on Alpine

License

Notifications You must be signed in to change notification settings

dzikus/docker-backuppc

 
 

Folders and files

NameName
Last commit message
Last commit date

Latest commit

 

History

53 Commits
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 
 

Repository files navigation

github.com/tiredofit/docker-backuppc

GitHub release Build Status Docker Stars Docker Pulls Become a sponsor Paypal Donate


About

This will build a Docker image for BackupPC - A backup system.

Maintainer

Table of Contents

Prerequisites and Assumptions

  • Assumes you are using some sort of SSL terminating reverse proxy such as:
  • Make sure there is adequate storage available to perform deduplicated backups!

Installation

Build from Source

Clone this repository and build the image with docker build -t (imagename) .

Prebuilt Images

Builds of the image are available on Docker Hub and is the recommended method of installation.

docker pull tiredofit/backuppc:(imagetag)

The following image tags are available along with their tagged release based on what's written in the Changelog:

Container OS Tag
Alpine :latest

Configuration

Quick Start

  • The quickest way to get started is using docker-compose. See the examples folder for a working docker-compose.yml that can be modified for development or production use.

  • Set various environment variables to understand the capabilities of this image.

  • Map persistent storage for access to configuration and data files for backup.

  • Enter inside the container and as user backuppc ssh-copy-id your public keys to a remote host

  • Visit your Web interface

Persistent Storage

The following directories are used for configuration and can be mapped for persistent storage.

Directory Description
/var/lib/backuppc The backed up Data
/etc/backuppc Configuration Files
/home/backuppc Home Directory for Backuppc (SSH Keys)
/www/logs Logfiles for Nginx, Supervisord, BackupPC, Zabbix

Environment Variables

Base Images used

This image relies on an Alpine Linux or Debian Linux base image that relies on an init system for added capabilities. Outgoing SMTP capabilities are handlded via msmtp. Individual container performance monitoring is performed by zabbix-agent. Additional tools include: bash,curl,less,logrotate, nano,vim.

Be sure to view the following repositories to understand all the customizable options:

Image Description
OS Base Customized Image based on Alpine Linux
Nginx Nginx webserver
Variable Description
BACKUPPC_UUID The uid for the backupp