Podman rootless, using quadlets for systemd services. :D
Podman rootless, using quadlets for systemd services. :D
Check out the following link - I am pretty sure its what I used to get it all working.
https://3os.org/infrastructure/proxmox/gpu-passthrough/igpu-passthrough-to-vm/
Hey, sorry for the late reply. I am running rootless using a dedicated user, so I use systemctl --user
to control the container.
From what I understand, when running rootless the root user inside the container correlates to the outside user (which is running the container), in terms of permissions. The external directories I bind mount into the container as externally owned by my dedicated user, so that the root user inside the container owns them (inside the container).
Are you doing rootless or rootfull podman? I am doing rootless and I have the following in my radarr container - PUID=0 PGID=0
I am using Calibre-Web mostly - but I have run into issues with thumbnail generation after my collection hit around 500000 books. I am just over 600000 now, but a large swathe don’t have thumbnails unless I do a manual metadata search. I should probably look for an alternative, but at this point I CBF.
Yeah it looks pretty slick but not so much slicker than Frigate that I will pay to be in the beta. :)
Personally I would lean towards finding out why its borking with SELinux and fixing that. It really shouldn’t be too hard. As others have mentioned it may be as simple as how you are mounting volumes into your containers - or it could be changing the SELinux context type for some files.
I like how K-9 hooks directly into OpenKeychain for encryption. Does Fairemail do that?
It says it is “a” standard file system - not “the” standard. Very different things.
So for Linux that would be ext4.
It’s worth noting that the default file system varies by distro - there is no ‘Linux’ default. For example, RHEL et al use XFS as the default.
No madness. I know it works natively. I also know it works perfectly well with a rootfull container.
All of my other applications are running in containers and having Plex also run in a container would simplify my overall architecture and recovery, should I need to replace the host.
Not very helpful.
Yeah this was it. Disabled rocket and it now works fine.
Yes I bet this is it. I’ll disable and test. Thanks for the heads up!
Thanks for these. It’s good to see someone else building them!
I have the same problem using your 0.18.3 lemmy-ui image as I do when I build it - it just doesn’t seem to work on my instance. None of the feed loads up and the selector buttons don’t either.
Is it working for you?
I’m doing that. 4 core arm instance with 24GB ram. It’s on a paid account but using free tier.
Random guy here saying I’ve built arm64 v0.17.4…
Available on docker hub search for mpatton.
I built my own arm64 v0.17.4 docker image. It’s available on docker hub:
mpatton/lemmy:0.17.4-linux-arm
mpatton/lemmy-ui:0.17.4-linux-arm
What are you using as your reverse proxy?
Amazon was in the infrastructure business well before containers were the “big thing”.