o/1MS\o ⌨️🐧 | #WeAreNatenom

@captcha_incorrect Currently I’m running my personal services similar to you using Podman Quadlets and I really like it.
I have also a testing installation of Proxmox on another system, but I’m also not so clear, if it would be a good way for my purposes.

@Nickelalloy Maybe Back In Time is a possible solution.
Its using rsync and it is possible to be scheduled.

https://github.com/bit-team/backintime

@JelleWho I’m running Home Assistant as container with podman quadlet.
I’m using an Ansible Playbook, which is executed manually for updating of Home Assistant.

If a new HA container image has been fetched, the podman quadlet is stopped, a backup of the container volumes is executed and afterwards the podman quadlet is started again, using the new container image for the container.

@Epzillon Don’t know, if it fits your needs, I’m currently running https://tvheadend.org/ and MiniDLNA https://sourceforge.net/projects/minidlna/ on an Odroid XU4Q with Arch Linux Arm.
My TV can direct use DLNA, so no further software is necessary.

Tvheadend is recording actual tv shows and recordings are manually converted into h264 videos afterwards and placed on the DLNA server.
Shows, which I don’t want to archive, are also served by the DLNA server.

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

deleted by creator

@Excaliburr Yes, you are right.

Do you have already a single container running with rootless podman?
Your given Arr-Stack seems to me relative complex when you are a beginner with podman.
Probably you could get some experience, when you start with just a single container.

In following posts are my personal quadlet settings for running Portainer, which could be helpful for getting insights of your running containers.

https://docs.portainer.io/start/install-ce/server/podman/linux

[Install]  
\# Start by default on boot without explicit enabling  
\# To avoid automatic start Install section has to be  
\# disabled  
WantedBy=default.target multi-user.target

[Service]  
\# Restart service in case of failures  
Restart=on-failure  
TimeoutStartSec=20  
TimeoutStopSec=20  
Type=notify  

[Container]  
AutoUpdate=registry  
ContainerName=con-portainer  
HostName=con-portainer  
Image=docker.io/portainer/portainer-ce:lts  
Notify=conmon  
PublishPort=8000:8000  
PublishPort=9443:9443  
Pull=missing  
Volume=vol-portainer:/data  
Volume=%t/podman/podman.sock:%t/podman/podman.sock  

[Unit]  
Description=Container running Portainer container management platform  
Wants=podman-user-wait-network-online.service  
After=podman-user-wait-network-online.service  
After=local-fs.target  
Requires=podman.socket  

Maybe you have to check Volume and Port settings, so that it fit your needs.

I always prefix my containers with “con-”, so that it is easier to finding them with systemctl --user.

@Excaliburr 3. Are we talking here about rootless podman? If yes, containers are running on the host with the uid of current user, in your example with UID 1000.
Processes IN started containers are often running with UID=0, but this belongs to definition of used container and is only IN container.
PostgreSQL in Debian container is running with UID=999.
To avoid problems with created files in host file system, I’m using UserNS=keep-id:uid=999,gid=999, which maps files to the UID on host system.