Zamba LXC Toolbox a script collection to setup LXC containers on Proxmox + ZFS. Zamba is the fusion of ZFS and Samba (standalone, active directory dc or active directory member), preconfigured to access ZFS snapshots by "Previous Versions" to easily recov
Go to file
2023-02-12 16:10:47 +01:00
conf Remove incomplete services, fix zmb.conf 2023-02-12 16:05:32 +01:00
scripts move nextcloud updater 2022-11-08 23:42:39 +01:00
src Remove incomplete services, fix zmb.conf 2023-02-12 16:05:32 +01:00
.gitignore Moved zamba.conf.example to conf folder 2021-04-27 11:17:02 +02:00
install.sh zmb-ad-join: set dns server after install 2023-02-12 15:09:17 +01:00
LICENSE Create LICENSE 2021-04-15 23:13:43 +02:00
README.md Readme: add omada 2023-02-12 15:59:43 +01:00

Zamba LXC Toolbox

About

Zamba LXC Toolbox is a collection of scripts to easily install Debian LXC containers with preconfigured services on Proxmox with ZFS. The main feature is Zamba, the fusion of ZFS and Samba in three different flavours (standalone, active directory dc or active directory member), preconfigured to access ZFS snapshots by "Windows Previous Versions" to easily recover encrypted by ransomware files, accidently deleted files or just to revert changes. The package also provides LXC container installers for mailpiler, matrix-synapse + element-web and more services will follow in future releases.

Requirements

Proxmox VE Server (>=6.30) with at least one configured ZFS Pool.

Included services:

  • bookstack => Bookstack wiki software bookstackapp.com
  • checkmk => Check_MK 2.0 Monitoring Server checkmk.com
  • debian-priv => Debian privileged container with basic toolset
  • debian-unpriv => Debian unprivileged container with basic toolset
  • ecodms => Fullfeatured DMS ecodms.de
  • gitea => Lightweight and fast self-hosted git service gitea.io
  • kimai => Kimai Time-Tracking kimai.org
  • kopano-core => Kopano Core Groupware kopano.io
  • mailpiler => mailpiler mail archive mailpiler.org
  • matrix => Matrix Synapse Homeserver matrix.org with Element Web Element on github
  • nextcloud => Nextcloud Server nextcloud.com with fail2ban und redis configuration
  • omada => TP-Link Omada SDN Controller www.tp-link.com
  • onlyoffice => OnlyOffice onlyoffice.com
  • open3a => Open3a web based accounting software open3a.de
  • proxmox-pbs => Proxmox Backup Server proxmox.com
  • unifi => Unifi Controller ui.com
  • urbackup => UrBackup Server urbackup.org
  • vaultwarden => Bitwarder compatible Passwordmanager github.com/dani-garcia/vaultwarden
  • zabbix => Zabbix Monitoring server zabbix.com
  • zammad => Zammad Helpdesk and Ticketing Software zammad.org
  • zmb-ad => ZMB (Samba) Active Directory Domain Controller, DNS Backends SAMBA_INTERNAL and BIND9_DLZ are supported
  • zmb-ad-join => Additional Active Directory Domain Controller joining an existing Domain
  • zmb-member => ZMB (Samba) AD member with ZFS volume snapshot support (previous versions)
  • zmb-standalone => ZMB (Samba) standalone server with ZFS volume snapshot support (previous versions)

Usage

Just ssh into your Proxmox machine and clone this git repository. Make sure you have installed git.

apt update
apt -y install git

Clone this Repository

git clone https://github.com/bashclub/zamba-lxc-toolbox
cd zamba-lxc-toolbox

Configuration

Copy zamba.conf.example located in conf directory to a new file (default: zamba.conf) and adjust your desired settings. For further information about configuration variables, have a look at conf/README.md

cp conf/zamba.conf.example conf/zamba.conf

Installation

After configuring, you are able to launch the script interactively (only works with conf/zamba.conf):

bash install.sh

Advanced Usage

You can set optional parameters (config file, service, container id):

Example:

bash install.sh -i 280 -c conf/my-zmb-service.conf -s zmb-member

You can also view possible parameters with install.sh -h

After container creation, you will be prompted to select the service to install and depending on the service there may be some more questions during installation.

Once the script has finished, the container is installed and running and you can continue with the service specific configuration.