
I can confirm that upgrading to 158.0.2 fixed it for me (I tested right before the update and it was still trusting the corresponding CA, and after updating it doesn’t anymore).
score 1 · canonical

I can confirm that upgrading to 158.0.2 fixed it for me (I tested right before the update and it was still trusting the corresponding CA, and after updating it doesn’t anymore).
score 1 · canonical

I’m also on 158.0.1 (Samsung Galaxy S26 Ultra, Android 17) and restarting my phone didn’t fix it.
score 1 · canonical

The real alternative is using run0 but I am not sure if it’s globally available now.
score 1 · canonical

So far, apart from not being able to publish root-reserved ports, the only thing I found is that internal networks are in fact not internal.
score 1 · canonical

I moved my deployments to Podman Quadlet too. Wanted to make an article for this at first but it is a too large chunk to write.
I still use docker-compose at work (for development purposes), when I get a Linux machine. It’s easier to show that I’m using the same tool as everyone (while underlying it’s not really Docker).
score 1 · canonical

Last time I checked, podman-compose missed a lot of features and was easy to break. It probably evolved since then, but I kept using docker-compose since that time.
Adding a link to it nonetheless.
score 1 · canonical

On my system (Arch Linux), the Podman socket (systemd’s socket activation) is not started by default.
Good suggestion for the other user part.
EDIT: It doesn’t seem to work when part of the wheel group, unlike machinectl. Probably requires root.
score 1 · canonical
Unfortunately this setting makes external app links open in the current tab too, so I had to revert.
score 1 · canonical