Selfhosted
A place to share alternatives to popular online services that can be self-hosted without giving up privacy or locking you into a service you don't control.
Rules:
-
Be civil: we're here to support and learn from one another. Insults won't be tolerated. Flame wars are frowned upon.
-
No spam posting.
-
Posts have to be centered around self-hosting. There are other communities for discussing hardware or home computing. If it's not obvious why your post topic revolves around selfhosting, please include details to make it clear.
-
Don't duplicate the full text of your blog or github here. Just post the link for folks to click.
-
Submission headline should match the article title (don’t cherry-pick information from the title to fit your agenda).
-
No trolling.
Resources:
- selfh.st Newsletter and index of selfhosted software and apps
- awesome-selfhosted software
- awesome-sysadmin resources
- Self-Hosted Podcast from Jupiter Broadcasting
Any issues on the community? Report it using the report flag.
Questions? DM the mods!
view the rest of the comments
Whichever one is better supported by the containers you want to run.
They both support the same containers
Except in real life you'll run into images that podman refuses to work with all the time.
Example? Ive definitely had compose projects that I had a hard time running with podman but all the individual containers seem to work just fine.
How do you make podman run an image that runs as an uid/gid that don't exist on the host and needs to access host devices/volumes owned by uid/gid that don't exist in the container?
You use podman unshare to
chownthe directories to the appropriate UID/GID in the container's user namespace.This right here. Just found out about this last week after a long debug.