![](/static/253f0d9b/assets/icons/icon-96x96.png)
![](https://lemmy.world/pictrs/image/db7182d9-181a-45e1-b0aa-6768f144911a.jpeg)
Temba, his arms open
Temba, his arms open
There are billions of us, we can look at more than one angle at a time. If we can’t all help on the issue du jour we should just pack it in?
Or let’s talk about how that air travel metric is likely bullshit. We barely do full lifecycle emissions for cars, do you think that metric did that for planes? Their tires? Their mandatory retirement duty cycle for all kinds of components up to their frames? They aren’t expensive as hell for the prestige of it.
But it’s actually a problem. It measures whole percentage points, it’s not a rounding error.
Dismissing an issue or person because conservatives are also using it as a punching bag doesn’t remove the problem, it just lets the conservatives control the narrative. I don’t think participating in that polarizing behavior is good or useful.
Almost everyone has a negligible impact when taken individually, that’s no excuse. Flying is terrible, private jets even more so.
You started a thread here explicitly asking for docker compose files that work on podman, but implicitly you want files that don’t have your particular issues. What issue are you having? It could be that it’s a setup/config issue and not a compose problem. Podman is specifically compatible with rocker and its tools, where I’ve seen people just alias docker to podman on their systems and keep working.
I doubt that all of your containers are all having unique problems. So sharing one or two of the common blockers, and how you have tried to work around them, would help a lot in what kinds of compose files you are looking for.
For instance, can you run a compose that is just a single Redis container? Just share it here, help us help you.
Can you share anything specific? Maybe some error messages or the behavior you are seeing? Podman has been running my compose files without issue, but I’m also just running a few simple services in each.
Kinda. You can copy your snapshots from @home too, meaning a restore from backup also restores your local file version history. There are also tools to push snapshots around as a large archive instead of dealing with smaller files directly.
The COW can also reduce the chances of running rsync on a large file that is currently being accessed, and getting a partial file in your backup. Or I suck at rsync 🤷♂️