80
Is it time to switch to podman?
(lemmy.ml)
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 26 Oct 2023
80 points (94.4% liked)
Selfhosted
59794 readers
313 users here now
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.
-
Posts here are to be centered around self-hosting. Please ensure it is clear in your post how it relates to self-hosting.
-
Don't duplicate the full text of your blog or git here. Just post the link for folks to click.
-
Submission headline should match the article title.
-
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!
founded 3 years ago
MODERATORS
But you don't need to have systemd run anything (except docker or podman itself). Just run containers with "restart: always" and docker/podman will start them on boot, restart them of they fail, and leave them alone if they're manually stopped.
You only need to run compose when you are [re]provisioning a container.
Podman does not start your containrs on boot. You need to do some magic yoursefel. Like a cronjob that starts all containers at boot.
When you used the Podman systemd integration it starts containers on boot just fine. You can even configure it to auto-update containers. Very hassle free.