podman-compose definitely got better over the past year…

But you can also use docker-compose itself with podman instead!

https://www.redhat.com/en/blog/podman-docker-compose

Basically, for system level containers, you can do:

sudo systemctl start podman.socket

(or enable --now instead of start if you want it to stick around after rebooting)

Then use docker-compose and it’ll communicate with podman instead of docker.

For user session “rootless” containers, it’s mainly the same thing, except you’ll need to remove sudo and then add --user after start or enable in that systemctl command. And you’d need to set an environment variable (either prefixing it on the command or using export to set it in your session), like this:

DOCKER_HOST=unix:///run/user/$UID/podman/podman

(Put that in front of the docker-compose command and it’ll connect to podman as your user instead, provided the service is available. Or toss it into your .bashrc with "export " before it and new bash sessions would have it.)

https://brandonrozek.com/blog/rootless-docker-compose-podman/

The one big gotcha I’ve hit is that if you have SELinux on your system, you’ll want to add :z to your volume(s) mount to have it automatically deal with SELinux stuff. (Lowercase z for volumes that can be mounted for multiplayer containers and uppercase Z for volumes that are tied to a specific container.)

But, I’ve found that using “quadlet” service files is much, much better than using podman-compose or docker-compose. There’s a program called “podlet” that can even convert compose files to service files (quadlet)… It can convert command line flags and kubes and other formats too.

Quadlets are basically systems service files that integrate with podman, letting you easily set up a container as a system (or even user level) service, making managing a container just like managing any other service.

Here’s the podlet command that’ll convert things to quadlets: https://github.com/containers/podlet

I basically gave up on podcasts on the desktop and only use AntennaPod on my phone. When I’m at my desktop, I have my phone paired with my computer via Bluetooth and play that way. I can pause it on my computer via KDE Connect (GSConnect on GNOME).

Bluetooth audio from phone to desktop works on Fedora Linux quite well. It probably works on other Linux distros too. I’m guessing it might also work on other OSes like Windows and macOS.

KDE Connect is available on Android, iOS, KDE (and can run on other desktops too), GNOME (via the GSConnect extension), Windows, and macOS.

This solves the syncing problem by sidestepping the need for it. My podcast state is always correct and I always have my podcasts with me, even when out and about.

Docker on Windows and Mac also runs containers through a VM though. (It’s more obvious on Windows, where you need WSL (powered by a VM) and Hyper-V (a way to run VMs on Windows). But on a Mac, VMs to run Linux are also used to run Docker containers inside the VM.)

Podman Desktop helps to abstract VMs away on Windows and macOS: https://podman-desktop.io/

For the command line, there’s “podman machine” to abstract away the VM. https://podman.io/docs/installation (installing on macOS is mentioned on that page and Windows has a link to more docs which also uses the podman machine command.)

As for Docker compose, you can use it directly with Podman too: https://www.redhat.com/sysadmin/podman-docker-compose (there’s also podman-compose as well). The only thing Docker compose doesn’t support with Podman is swarm functionality.

Docker compose can even work with rootless Podman containers on a user account. It requires an environment variable. https://major.io/p/rootless-container-management-with-docker-compose-and-podman/ (it’s basically enabling the socket for podman and using the environment variable to point at the user podman socket)

You can set up mount points on Linux, at least in GNOME, very easily. (It’s even fully automatic for external disks.) I’d be surprised if it isn’t as easy in KDE and other desktops too.

The problem here (at least from what it sounds like) isn’t setting up mount points. The problem is fixing an incorrect fstab on the disk that’s causing the system to hang on boot.

(This isn’t a typical situation, which is why I also asked about how the partition was added to the system.)

Good point! GNOME Disks can do this, actually. I didn’t think about that.

(Edit: However, I think it’ll just edit the /etc/fstab of the running system. In other words, the one of the live session, not the one on the installation.)

My first attempt to try to fix something like this would be to:

1. Download Fedora Workstation live media. (Within Windows or some other computer that boots.)
2. Flash it to a USB stick.
3. Reboot to the live desktop from the USB stick. (It might require pressing F12 or some other key combo during boot.)
4. “Try out” Fedora. (That is: do not install.)
5. Open GNOME Disks. (I think it’s included. Otherwise, you can sudo dnf install gnome-disks to install it temporarily on the live session.)
6. Try to mount the main filesystem that contains /etc/fstab (it should ask you for the LUKS password.
7. Comment out the Windows mount point. Or if you want to keep it (if the partition still exists and is just “dirty” and still needs a check from Windows) add “,nofail” after “auto” to the options in the line for the mount, so your system should still boot without that mount point.
8. Save the /etc/fstab file.
9. Shut down the computer.
10. Unplug USB stick.
11. Boot computer. Linux should successfully boot… hopefully. 😉

I’m also wondering: How did you add the Windows partition to Fedora? Was it from within Fedora’s installer (aka: “Anaconda”)? Or did you add it in a different way?

(BTW: I use Silverblue and have a long history with Fedora. 😁)

Also: Inspector Gadget.

An international US, French, and Canadian production.

Penny (the “hacker” niece) and Brain (the intelligent dog) solve all of the cases that Inspector Gadget (cyborg cop) bumbles through, even though he’s essentially RoboCop with gimmicks.

It’s not necessarily that smoking is a larger percentage of the population. It varies, but stats show a similar percentage more or less… it is a bit higher in Europe on average than in the US on average — but both places are large with varied amounts of smokers. It’s more that people are outside near each other more in Europe.

https://worldpopulationreview.com/country-rankings/smoking-rates-by-country

In Europe they’re walking down the street, sitting outdoors at cafes, hanging out in the city center, etc. Whereas in the US, people are often driving from place to place to go to a destination, so you don’t notice the smoking as much. Plus, smoking sections are a concept that exists in the US (even outside), whereas they don’t in Europe. Thankfully, in much of the US and EU, most places are finally non-smoking indoors now.

This is a gross overgeneralization. It’s different in different parts of the US and different parts of Europe, of course.

(FWIW: I totally agree with you that it’s gross. And it’s far too common to run into in Europe.)