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

[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  

@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

[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  

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.

[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  

@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.