Archive for the ‘Raspberry Pi’ Category
Raspberry Pi Imager 2.0 – it brings a new wizard interface the opportunity to pre configure Raspberry Pi Connect, and improved accessibility for screen readers and other assistive technologies
Dienstag, November 25th, 2025Home Lab 2025 – 15 Docker containers that instantly improve your IT environment in late 2025
Freitag, November 21st, 2025UGREEN NASync DH4300 Plus – in 10 Minuten Paperless NGX installieren
Freitag, November 21st, 2025Raspberry Pi – how to run all Intel GPUs
Donnerstag, November 20th, 2025Watchtower & Portainer – automatische Docker Updates einfach erklärt
Dienstag, November 11th, 2025Zabbix 8.0 – a new chapter in Monitoring by Alexei Vladishev
Montag, November 3rd, 2025Home Lab 2025 – Server Monitoring Tool ‚Beszel‘ with a Docker/Portainer Setup in Minutes and Easy to Use
Mittwoch, Oktober 22nd, 2025

To uninstall the Beszel agent run the installation script with the -u option
pi@rpi-NodeRed-01:~ $
pi@rpi-NodeRed-01:~ $ curl -sL https://get.beszel.dev -o /tmp/install-agent.sh && chmod +x /tmp/install-agent.sh && /tmp/install-agent.sh -u
Stopping and disabling the agent service…
Removed /etc/systemd/system/multi-user.target.wants/beszel-agent.service.
Removing the systemd service file…
Removing the daily update service and timer…
Removing the Beszel Agent directory…
Removing the dedicated user for the agent service…
Beszel Agent has been uninstalled successfully!
pi@rpi-NodeRed-01:~ $
Docker & Portainer – eine Schritt-für-Schritt Installationsanleitung
Mittwoch, Oktober 22nd, 2025docker run -d -p 8000:8000 -p 9443:9443 –name=portainer –restart=always -v /var/run/docker.sock:/var/run/docker.sock -v portainer_data:/data portainer/portainer-ce:latest

Podman & MinIO S3 Storage – mit Proxmox Virtual Environment (VE) 9.0.10 Container (LXC) Ubuntu 25.04 installieren für eine Backup Strategie ‚ProtectIT‘
Freitag, Oktober 10th, 2025The –dry-run option ensures that only the availability of new images is checked but no pull operations are performed and no new containers are created
root@pve-pdman-01:~# apt-get install podman -y
root@pve-pdman-01:~# podman -v
podman version 5.4.1
root@pve-pdman-01:~# podman info
root@pve-pdman-01:~# mkdir -p ~/minio/data
root@pve-pdman-01:~# podman run \
-p 9000:9000 \
-p 9001:9001 \
–name minio \
-v ~/minio/data:/data \
-e „MINIO_ROOT_USER=<user>“ \
-e „MINIO_ROOT_PASSWORD=<password>“ \
quay.io/minio/minio server /data –console-address „:9001“
root@pve-pdman-01:~# podman images
REPOSITORY TAG IMAGE ID CREATED SIZE
quay.io/minio/minio latest 69b2ec208575 2 weeks ago 176 MB
root@pve-pdman-01:~# podman ps
CONTAINER ID IMAGE COMMAND CREATED STATUS PORTS NAMES
86234ac671bb quay.io/minio/minio:latest server /data –co… About an hour ago Up 9 minutes 0.0.0.0:9000-9001->9000-9001/tcp minio
http://<IP@>:9001

The –dry-run option ensures that only the availability of new images is checked but no pull operations are performed and no new containers are created
root@pve-pdman-01:~# podman auto-update –dry-run
root@pve-pdman-01:~#
root@pve-pdman-01:~# curl https://dl.min.io/client/mc/release/linux-amd64/mc \
–create-dirs \
-o $HOME/minio-binaries/mc
root@pve-pdman-01:~# chmod +x $HOME/minio-binaries/mc
root@pve-pdman-01:~# export PATH=$PATH:$HOME/minio-binaries/
root@pve-pdman-01:~# mc –help
The mc alias set command sets or updates an alias in the MinIO client configuration
root@pve-pdman-01:~# mc alias set myminio http://192.168.1.177:9000 <user> <password>
Added `myminio` successfully.
root@pve-pdman-01:~#
Enables object optional locking on the specified bucket and object locking requires and therefore implies enabling object versioning:
–with-lock
root@pve-pdman-01:~# mc mb –with-lock myminio/worm-with-versioning-and-retention–day
Bucket created successfully `myminio/worm-with-versioning-and-retention–day`.
root@pve-pdman-01:~#
root@pve-pdman-01:~# mc ilm add –expiry-days 15 myminio/worm-with-versioning-and-retention–day
Lifecycle configuration rule added with ID `d3dsfjcukqlgnr42cv90` to myminio/worm-with-versioning-and-retention–day.
root@pve-pdman-01:~#
root@pve-pdman-01:~# mc ilm rule rm –id „d3dsfjcukqlgnr42cv90“ myminio/worm-with-versioning-and-retention–day
Rule ID `d3dsfjcukqlgnr42cv90` from target myminio/worm-with-versioning-and-retention–day removed.
root@pve-pdman-01:~#
The optiml number of days to retain an object after being created:
–expire-days
root@pve-pdman-01:~# mc ilm add –expiry-days 12 myminio/worm-with-versioning-and-retention–day
Lifecycle configuration rule added with ID `d3f7j1cukqlhid0kvulg` to myminio/worm-with-versioning-and-retention–day.
root@pve-pdman-01:~#
The optional number of days to retain an object version after becoming non-current:
–noncurrent-expire-days
root@pve-pdman-01:~# mc ilm add –insecure –noncurrentversion-expiration-days 3 myminio/worm-with-versioning-and-retention–day
Lifecycle configuration rule added with ID `d3dsgocukqlgnqqqgmi0` to myminio/worm-with-versioning-and-retention–day.
root@pve-pdman-01:~#
root@pve-pdman-01:~# mc ilm export myminio/worm-with-versioning-and-retention–day
{
„Rules“: [
{
„ID“: „d3dsgocukqlgnqqqgmi0“,
„NoncurrentVersionExpiration“: {
„NoncurrentDays“: 3
},
„Status“: „Enabled“
},
{
„Expiration“: {
„Days“: 12
},
„ID“: „d3f7j1cukqlhid0kvulg“,
„Status“: „Enabled“
}
]
}
root@pve-pdman-01:~#
root@pve-pdman-01:~# mc ilm add –expiry-days 96 myminio/worm-with-versioning-and-retention–week
root@pve-pdman-01:~# mc ilm add –noncurrentversion-expiration-days 3 myminio/worm-with-versioning-and-retention–week
root@pve-pdman-01:~# mc ilm add –expiry-days 192 myminio/worm-with-versioning-and-retention–month
root@pve-pdman-01:~# mc ilm add –noncurrentversion-expiration-days 3 myminio/worm-with-versioning-and-retention–month
root@pve-pdman-01:~# mc ilm add –expiry-days 484 myminio/worm-with-versioning-and-retention–year
root@pve-pdman-01:~# mc ilm add –noncurrentversion-expiration-days 3 myminio/worm-with-versioning-and-retention–year

root@pve-pdman-01:~#
root@pve-pdman-01:~# mc retention set –default compliance 7d myminio/worm-with-versioning-and-retention–day
Object locking ‚COMPLIANCE‘ is configured for 7DAYS.
root@pve-pdman-01:~# mc retention info myminio/worm-with-versioning-and-retention–day
Object locking ‚COMPLIANCE‘ is configured for 7DAYS.
root@pve-pdman-01:~# mc –json retention info myminio/worm-with-versioning-and-retention–day
{
„op“: „info“,
„enabled“: „Enabled“,
„mode“: „COMPLIANCE“,
„validity“: „7DAYS“,
„status“: „success“
}
root@pve-pdman-01:~#
The MinIO mc mirror command synchronizes content to MinIO deployment similar to the ‚rsync‘ utility
root@rpi-iot-jsho-cam-02:~# mc mirror –json $LocalBackupPath/$MirrorDay $MinioBucket/MotionEYE/$MirrorDay
root@pve-pdman-01:~#
root@pve-pdman-01:~# mc admin info myminio
● 192.168.1.177:9000
Uptime: 3 days
Version: 2025-09-07T16:13:09Z
Network: 1/1 OK
Drives: 1/1 OK
Pool: 1
┌──────┬──────────────────────┬─────────────────────┬──────────────┐
│ Pool │ Drives Usage │ Erasure stripe size │ Erasure sets │
│ 1st │ 4.5% (total: 59 GiB) │ 1 │ 1 │
└──────┴──────────────────────┴─────────────────────┴──────────────┘
1005 MiB Used, 1 Bucket, 18,041 Objects, 18,042 Versions, 1 Delete Marker
1 drive online, 0 drives offline, EC:0
root@pve-pdman-01:~#
root@pve-pdman-01:~# mc tree myminio
myminio
└─ worm-with-versioning-and-retention–day
└─ MotionEYE
├─ Camera1
│ ├─ 2025-10-01
│ ├─ 2025-10-02
│ ├─ 2025-10-03
│ ├─ 2025-10-04
│ ├─ 2025-10-05
│ ├─ 2025-10-06
│ ├─ 2025-10-07
│ └─ 2025-10-08
├─ Camera2
│ ├─ 2025-10-01
│ ├─ 2025-10-02
│ ├─ 2025-10-03
│ ├─ 2025-10-04
│ ├─ 2025-10-05
│ ├─ 2025-10-06
│ ├─ 2025-10-07
│ └─ 2025-10-08
├─ Camera3
│ ├─ 2025-10-01
│ ├─ 2025-10-02
│ ├─ 2025-10-03
│ ├─ 2025-10-04
│ ├─ 2025-10-05
│ ├─ 2025-10-06
│ ├─ 2025-10-07
│ └─ 2025-10-08
└─ Camera4
├─ 2025-10-01
├─ 2025-10-02
├─ 2025-10-03
├─ 2025-10-04
├─ 2025-10-05
├─ 2025-10-06
├─ 2025-10-07
└─ 2025-10-08
root@pve-pdman-01:~#

root@pve-pdman-01:~#
root@pve-pdman-01:~# mc mb –with-lock myminio/worm-with-versioning-and-retention–week
Bucket created successfully `myminio/worm-with-versioning-and-retention–week`.
The mc rb command remove an empty bucket


