jean/docu
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

Doku: CT 100 files unter pve1/guests/ct100-files.

Browse Source 
Samba, Proxmox-Config, Host-NFS-Exports; pve1-Gäste komplett.

Co-authored-by: Cursor <cursoragent@cursor.com>
This commit is contained in:
root
2026-06-28 11:17:48 +02:00
parent 805b6d3534
commit 842e66996f
9 changed files with 429 additions and 6 deletions
Download Patch File Download Diff File Expand all files Collapse all files
pve1/00_README.md
+1 -1
View File
@@ -30,7 +30,7 @@
- **Keine NVIDIA-GPU** → Power-Agent nur CPU (Intel RAPL)
- **Fallback-OPNsense** VM 104 — CARP-Backup parallel zu pve2 (advskew 100)
- CT **100** (files) — Datei-Server
- CT **100** (files) — [guests/ct100-files/](guests/ct100-files/) Samba/Cockpit, `/mnt/storage`
## ⛔ Agenten-Regel
pve1/06_ubuntu-vm-nextcloud.md
+2 -1
View File
@@ -21,8 +21,9 @@ pve1 (192.168.10.5)
└── … weitere Stacks (Gitea, Airsonic, Vaultwarden, …)
Daten:
/mnt/nextcloud-data ← NFS von pve1/CT files
/mnt/nextcloud-data ← NFS von **pve1-Host** (192.168.10.5), nicht CT 100
192.168.10.5:/mnt/storage/service_data/cloud/data (mergerfs-Pool, ~99 TB, ~95 % belegt)
Storage-CT: [guests/ct100-files/](guests/ct100-files/) (Samba/Cockpit, VLAN 20)
im Container: /data
Stack-Pfad auf der VM: /opt/stacks/nextcloud/
pve1/guests/README.md
+4 -3
View File
@@ -1,12 +1,13 @@
# Gäste auf pve1 — Stack-Konfiguration (Compose & Anhang)
# Gäste auf pve1 — Konfiguration (Stacks, Dienste, Anhang)
Compose-Dateien und stack-relevante Konfiguration **ohne** Volumes, Datenbanken, App-Daten oder Secrets.
Compose-Dateien, LXC-/Service-Konfiguration **ohne** Volumes, Datenbanken, App-Daten oder Secrets.
| Ordner | Gast | Host | Rolle |
|--------|------|------|-------|
| [vm101-ubuntu/](vm101-ubuntu/) | VM 101 `ubuntu` | pve1 | Docker-Host: Nextcloud, NPM, Gitea, … |
| [ct100-files/](ct100-files/) | CT 100 `files` | pve1 | Storage: Samba/Cockpit, Bind `/mnt/storage` |
**Live-Pfad auf dem Gast:** `/opt/stacks/<stack-name>/`
**Live-Pfade:** VM Docker → `/opt/stacks/<stack>/` · CT → `/etc/samba/`, Proxmox `pct config`
Passwörter in den Repo-Dateien sind durch `REDACTED` ersetzt. Live-Werte nur auf dem jeweiligen Gast.
pve1/guests/ct100-files/README.md
+149
View File
@@ -0,0 +1,149 @@
# CT 100 — files (Storage / Samba)
| | |
|---|---|
| **Proxmox** | pve1, CTID 100 |
| **Hostname** | `files` |
| **IP** | 192.168.20.10/24 (VLAN 20 Privat) |
| **Gateway/DNS** | 192.168.20.1 (OPNsense) |
| **Typ** | LXC — **kein Docker** |
Zentraler Dateizugriff auf den **mergerfs-Pool** `/mnt/storage` (~99 TB, via Bind-Mount vom pve1-Host).
---
## Rolle im Gesamtsystem
```
pve1 Host (192.168.10.5)
├── /mnt/storage ← mergerfs-Pool (Physisch auf Host)
├── /etc/exports ← NFS-Server (für VM 101, pve2)
└── mp0 → CT 100 ← gleicher Pfad im Container
CT 100 (192.168.20.10)
├── /mnt/storage ← Bind von Host
├── Samba [storage] ← SMB-Zugriff auf ganzen Pool
└── Cockpit ← Web-UI (file-sharing Modul)
VM 101 (192.168.10.10)
└── NFS von 192.168.10.5 ← Nextcloud-Daten, Media, Audio
(nicht von CT 100!)
```
**Wichtig:** NFS-Exports laufen auf dem **Proxmox-Host** (`192.168.10.5`), nicht im CT. Der CT dient vor allem **Samba/Cockpit** auf VLAN 20.
---
## Proxmox-Konfiguration
→ [proxmox.conf](proxmox.conf)
| Parameter | Wert |
|-----------|------|
| RAM | 1024 MB |
| Cores | 4 |
| rootfs | 2 GB (`local-lvm`) |
| mp0 | `/mnt/storage` → `/mnt/storage` |
| Netz | `vmbr0`, VLAN tag **20** |
| Features | `nesting=1` |
---
## Dienste im CT
| Dienst | Zweck |
|--------|-------|
| **smbd/nmbd** | Samba — Share `[storage]` → `/mnt/storage` |
| **Cockpit** | Web-Admin inkl. `cockpit-file-sharing` |
| **SSH** | Remote-Admin |
| **NFS-Server-Pakete** | installiert; aktive Exports liegen auf dem **Host** |
---
## Konfiguration im Repo
| Datei | Beschreibung |
|-------|--------------|
| [proxmox.conf](proxmox.conf) | `pct config 100` |
| [smb.conf](smb.conf) | Samba (Share `[storage]`, Cockpit-Registry-Include) |
| [cockpit.conf](cockpit.conf) | Cockpit WebService |
| [host-exports.reference](host-exports.reference) | NFS `/etc/exports` auf **pve1** (Referenz) |
Keine User-Daten, keine Passwörter (`/etc/samba/private/` nicht im Repo).
---
## NFS-Exports (Host pve1)
Referenz: [host-exports.reference](host-exports.reference)
| Export | Client | Zugriff | Nutzung |
|--------|--------|---------|---------|
| `/mnt/storage/service_data/cloud/data` | 192.168.10.10 (VM 101) | rw | Nextcloud-Daten |
| `/mnt/storage/media` | 192.168.10.10 | rw | Media-Stacks (Audio, Sabnzbd, …) |
| `/mnt/storage/service_data/audio` | 192.168.10.10 | rw | Audiobookshelf/Airsonic-Config |
| `/mnt/nvme1/backup` | 192.168.10.10 | ro | Backup-Mount |
| `/mnt/storage/media/movies` | 192.168.10.4 (pve2) | rw | Jellyfin o. ä. |
| `/mnt/storage/media/tvshows` | 192.168.10.4 (pve2) | rw | Jellyfin o. ä. |
VM 101 `fstab`-Beispiel:
```
192.168.10.5:/mnt/storage/service_data/cloud/data /mnt/nextcloud-data nfs defaults,nofail,_netdev 0 0
192.168.10.5:/mnt/storage/media /mnt/storage/media nfs defaults,nofail,_netdev 0 0
192.168.10.5:/mnt/storage/service_data/audio /mnt/service_data/audio nfs defaults,nofail,_netdev 0 0
```
---
## Storage-Layout (Top-Level `/mnt/storage`)
| Pfad | Inhalt (Kurz) |
|------|----------------|
| `backup/` | Backups |
| `media/` | Filme, Serien, Musik (NFS an VM 101 / pve2) |
| `service_data/cloud/data/` | Nextcloud User-Daten (~93 TB belegt) |
| `service_data/audio/` | Audio-Stack-Daten |
| `projects/` | Projekte |
| `public/` | Öffentliche Shares |
| `homes/` | User-Homes |
**Auslastung (Stand Doku):** ~95 % — siehe [06_ubuntu-vm-nextcloud.md](../../06_ubuntu-vm-nextcloud.md)
---
## Samba Share `[storage]`
Aus [smb.conf](smb.conf) (via Cockpit file-sharing):
- **Pfad:** `/mnt/storage`
- **read only:** No
- Zugriff: über Samba-Authentifizierung (Details in CT, nicht im Repo)
---
## Wartung / Zugriff
```bash
# Proxmox
pct enter 100
pct exec 100 -- systemctl status smbd
# Samba testen
pct exec 100 -- testparm -s
# NFS auf Host prüfen (nicht im CT!)
exportfs -v
systemctl status nfs-server
```
---
## Referenzen
| Dokument | Inhalt |
|----------|--------|
| [../vm101-ubuntu/](vm101-ubuntu/) | Docker-Stacks, NFS-Consumer |
| [../../06_ubuntu-vm-nextcloud.md](../../06_ubuntu-vm-nextcloud.md) | Nextcloud, Pool-Auslastung |
| [../../infrastructure-host.md](../../infrastructure-host.md) | pve1 CT/VM-Übersicht |
| [../../04_fallback_aktivierung.md](../../04_fallback_aktivierung.md) | VLAN 20 / Privat-Netz |
pve1/guests/ct100-files/cockpit.conf
+5
View File
@@ -0,0 +1,5 @@
[WebService]
AllowUnencrypted = false
[Session]
root = true
pve1/guests/ct100-files/host-exports.reference
+16
View File
@@ -0,0 +1,16 @@
# /etc/exports: the access control list for filesystems which may be exported
# to NFS clients. See exports(5).
#
# Example for NFSv2 and NFSv3:
# /srv/homes hostname1(rw,sync,no_subtree_check) hostname2(ro,sync,no_subtree_check)
#
# Example for NFSv4:
# /srv/nfs4 gss/krb5i(rw,sync,fsid=0,crossmnt,no_subtree_check)
# /srv/nfs4/homes gss/krb5i(rw,sync,no_subtree_check)
#
/mnt/storage/media/movies 192.168.10.4(rw,sync,no_subtree_check,async,fsid=1,insecure)
/mnt/storage/media/tvshows 192.168.10.4(rw,sync,no_subtree_check,async,fsid=2,insecure)
/mnt/storage/service_data/cloud/data 192.168.10.10(rw,sync,no_subtree_check,no_root_squash,fsid=3)
/mnt/nvme1/backup 192.168.10.10(ro,sync,no_subtree_check,no_root_squash,fsid=4)
/mnt/storage/media 192.168.10.10(rw,sync,no_subtree_check,no_root_squash,fsid=5)
/mnt/storage/service_data/audio 192.168.10.10(rw,sync,no_subtree_check,no_root_squash,fsid=6)
pve1/guests/ct100-files/proxmox.conf
+12
View File
@@ -0,0 +1,12 @@
arch: amd64
cores: 4
features: nesting=1
hostname: files
memory: 1024
mp0: /mnt/storage,mp=/mnt/storage
nameserver: 192.168.20.1
net0: name=eth0,bridge=vmbr0,hwaddr=BC:24:11:2E:6E:10,ip=192.168.20.10/24,tag=20,type=veth
onboot: 1
ostype: debian
rootfs: local-lvm:vm-100-disk-0,size=2G
swap: 512
pve1/guests/ct100-files/smb.conf
+239
View File
@@ -0,0 +1,239 @@
#
# Sample configuration file for the Samba suite for Debian GNU/Linux.
#
#
# This is the main Samba configuration file. You should read the
# smb.conf(5) manual page in order to understand the options listed
# here. Samba has a huge number of configurable options most of which
# are not shown in this example
#
# Some options that are often worth tuning have been included as
# commented-out examples in this file.
# - When such options are commented with ";", the proposed setting
# differs from the default Samba behaviour
# - When commented with "#", the proposed setting is the default
# behaviour of Samba but the option is considered important
# enough to be mentioned here
#
# NOTE: Whenever you modify this file you should run the command
# "testparm" to check that you have not made any basic syntactic
# errors.
#======================= Global Settings =======================
[global]
## Browsing/Identification ###
# Change this to the workgroup/NT-domain name your Samba server will part of
workgroup = WORKGROUP
#### Networking ####
# The specific set of interfaces / networks to bind to
# This can be either the interface name or an IP address/netmask;
# interface names are normally preferred
; interfaces = 127.0.0.0/8 eth0
# Only bind to the named interfaces and/or networks; you must use the
# 'interfaces' option above to use this.
# It is recommended that you enable this feature if your Samba machine is
# not protected by a firewall or is a firewall itself. However, this
# option cannot handle dynamic or non-broadcast interfaces correctly.
; bind interfaces only = yes
#### Debugging/Accounting ####
# This tells Samba to use a separate log file for each machine
# that connects
log file = /var/log/samba/log.%m
# Cap the size of the individual log files (in KiB).
max log size = 1000
# We want Samba to only log to /var/log/samba/log.{smbd,nmbd}.
# Append syslog@1 if you want important messages to be sent to syslog too.
logging = file
# Do something sensible when Samba crashes: mail the admin a backtrace
panic action = /usr/share/samba/panic-action %d
####### Authentication #######
# Server role. Defines in which mode Samba will operate. Possible
# values are "standalone server", "member server", "classic primary
# domain controller", "classic backup domain controller", "active
# directory domain controller".
#
# Most people will want "standalone server" or "member server".
# Running as "active directory domain controller" will require first
# running "samba-tool domain provision" to wipe databases and create a
# new domain.
server role = standalone server
obey pam restrictions = yes
# This boolean parameter controls whether Samba attempts to sync the Unix
# password with the SMB password when the encrypted SMB password in the
# passdb is changed.
unix password sync = yes
# For Unix password sync to work on a Debian GNU/Linux system, the following
# parameters must be set (thanks to Ian Kahan <<kahan@informatik.tu-muenchen.de> for
# sending the correct chat script for the passwd program in Debian Sarge).
passwd program = /usr/bin/passwd %u
passwd chat = *Enter\snew\s*\spassword:* %n\n *Retype\snew\s*\spassword:* %n\n *password\supdated\ssuccessfully* .
# This boolean controls whether PAM will be used for password changes
# when requested by an SMB client instead of the program listed in
# 'passwd program'. The default is 'no'.
pam password change = yes
# This option controls how unsuccessful authentication attempts are mapped
# to anonymous connections
map to guest = bad user
########## Domains ###########
#
# The following settings only takes effect if 'server role = classic
# primary domain controller', 'server role = classic backup domain controller'
# or 'domain logons' is set
#
# It specifies the location of the user's
# profile directory from the client point of view) The following
# required a [profiles] share to be setup on the samba server (see
# below)
; logon path = \\%N\profiles\%U
# Another common choice is storing the profile in the user's home directory
# (this is Samba's default)
# logon path = \\%N\%U\profile
# The following setting only takes effect if 'domain logons' is set
# It specifies the location of a user's home directory (from the client
# point of view)
; logon drive = H:
# logon home = \\%N\%U
# The following setting only takes effect if 'domain logons' is set
# It specifies the script to run during logon. The script must be stored
# in the [netlogon] share
# NOTE: Must be store in 'DOS' file format convention
; logon script = logon.cmd
# This allows Unix users to be created on the domain controller via the SAMR
# RPC pipe. The example command creates a user account with a disabled Unix
# password; please adapt to your needs
; add user script = /usr/sbin/useradd --create-home %u
# This allows machine accounts to be created on the domain controller via the
# SAMR RPC pipe.
# The following assumes a "machines" group exists on the system
; add machine script = /usr/sbin/useradd -g machines -c "%u machine account" -d /var/lib/samba -s /bin/false %u
# This allows Unix groups to be created on the domain controller via the SAMR
# RPC pipe.
; add group script = /usr/sbin/addgroup --force-badname %g
############ Misc ############
# Using the following line enables you to customise your configuration
# on a per machine basis. The %m gets replaced with the netbios name = files
# of the machine that is connecting
; include = /home/samba/etc/smb.conf.%m
# Some defaults for winbind (make sure you're not using the ranges
# for something else.)
; idmap config * : backend = tdb
; idmap config * : range = 3000-7999
; idmap config YOURDOMAINHERE : backend = tdb
; idmap config YOURDOMAINHERE : range = 100000-999999
; template shell = /bin/bash
# Setup usershare options to enable non-root users to share folders
# with the net usershare command.
# Maximum number of usershare. 0 means that usershare is disabled.
# usershare max shares = 100
# Allow users who've been granted usershare privileges to create
# public shares, not just authenticated ones
usershare allow guests = yes
#======================= Share Definitions =======================
# inclusion of net registry, inserted by cockpit-file-sharing:
include = registry
[homes]
comment = Home Directories
browseable = no
# By default, the home directories are exported read-only. Change the
# next parameter to 'no' if you want to be able to write to them.
read only = yes
# File creation mask is set to 0700 for security reasons. If you want to
# create files with group=rw permissions, set next parameter to 0775.
create mask = 0700
# Directory creation mask is set to 0700 for security reasons. If you want to
# create dirs. with group=rw permissions, set next parameter to 0775.
directory mask = 0700
# By default, \\server\username shares can be connected to by anyone
# with access to the samba server.
# The following parameter makes sure that only "username" can connect
# to \\server\username
# This might need tweaking when using external authentication schemes
valid users = %S
# Un-comment the following and create the netlogon directory for Domain Logons
# (you need to configure Samba to act as a domain controller too.)
;[netlogon]
; comment = Network Logon Service
; path = /home/samba/netlogon
; guest ok = yes
; read only = yes
# Un-comment the following and create the profiles directory to store
# users profiles (see the "logon path" option above)
# (you need to configure Samba to act as a domain controller too.)
# The path below should be writable by all users so that their
# profile directory may be created the first time they log on
;[profiles]
; comment = Users profiles
; path = /home/samba/profiles
; guest ok = no
; browseable = no
; create mask = 0600
; directory mask = 0700
[printers]
comment = All Printers
browseable = no
path = /var/tmp
printable = yes
guest ok = no
read only = yes
create mask = 0700
# Windows clients look for this share name as a source of downloadable
# printer drivers
[print$]
comment = Printer Drivers
path = /var/lib/samba/printers
browseable = yes
read only = yes
guest ok = no
# Uncomment to allow remote administration of Windows print drivers.
# You may need to replace 'lpadmin' with the name of the group your
# admin users are members of.
# Please note that you also need to set appropriate Unix permissions
# to the drivers directory for these users to have write rights in it
; write list = root, @lpadmin
pve1/infrastructure-host.md
+1 -1
View File
@@ -26,7 +26,7 @@ Netz: vmbr0 (WAN), vmbr1 (LAN) — siehe [02_netzwerk.md](02_netzwerk.md)
| CTID | Name | Status | Rolle |
|------|------|--------|-------|
| 100 | files | running | Datei-/Storage-CT |
| 100 | files | running | Datei-/Storage-CT — [guests/ct100-files/](guests/ct100-files/) |
## Dienste auf dem Host