towerful

Someone high up in the chain made it the messaging, tho.

MRFF has received over 200 calls from more than 50 military installations across all the services since Saturday reporting similar disturbing pronouncements from their Christian zealot commanders.

https://www.militaryreligiousfreedom.org/2026/03/mrff-inundated-with-complaints-of-gleeful-commanders-telling-troops-iran-war-is-part-of-gods-divine-plan-to-usher-in-the-return-of-jesus-christ/

Soubds like it's pretty unified messaging

Hdppy

"It's just the data we need to protect our business. It's legitimate interest, I promise"

You're telling me recon of the area never showed kids playing outside the building?!
What are they using, Google fucking maps?

Service accounts and RBAC has taken you for an absolute fool!

And it's still faster for my linux install to boot.
LUKS password for disk encryption, then user login to a usable desktop with network connectivity.
Windows takes ages to get to a login screen (bitlocker is disabled, so no decryption excuse), logging in is a breeze with fingerprint reader (certainly faster than typing in a password), then it sits there for ages looking like it's ready to be used, but the network stack isn't ready and it is just unusable until that comes up.

I'm so happy when I get a day of just working in Linux.
It just... Works.

I've had one issue in the past year and a half, dual booting from the same NVMe.
After fixing the boot partition issues from a liveUSB, the actual solution was disabling fast-boot.
It's been solid for a year now.

But I always shutdown my laptop when I'm not using it. And any windows updates that require restarts, I make sure it fully reboots into windows again.

As part of the "climbing out of the ground" cutscene, the demon roars with firey breath... Which burns off the scarf.

What's your vector, Victor?

Yeh, I don't quite understand docker desktop.
I guess it's handy for seeing running containers, volumes images etc.
But I don't get what it offers over CLI, or a TUI like lazy-docker.

You might be thinking of something like portainer, which does let you use compose files via its web gui.

Glad you've figured out the docker compose route. I find config files (and scripts) significantly easier to work with than figuring out a bunch of commands to run.

Yeh, it doesn't look like it's exposing the ports.
I don't know docker desktop.
I just use docker compose files, even for things that don't need it. I like having a file that describes the service, instead of deciphering run args.

Some googling,
https://stackoverflow.com/a/73819697
Describes how to run a container with more specifics.

I would strongly suggest you copy the official docker compose file, and run that with "docker compose up -d".
That will configure all the components required, then you can still inspect/stop/start/view etc using docker desktop.

But I also understand the brain fog.
Maybe you could work through the fog to install Portainer once. After which, you can use that and it's web GUI to manage all your containers and compose files.
Setup on Windows/WSL with Docker Desktop (but needs 2 commands: 1 to create the volume, 1 to run the container) https://docs.portainer.io/start/install-ce/server/docker/wsl

Portainer might be more what you are looking for, rather than docker desktop (although docker desktop does make docker installation a lot easier)

Reading https://github.com/wallabag/docker I don't see any mention of doc75/wallabag as an official image. Any reason you went with a 3rd party image?

Also, might be that you aren't exposing the port? Wallabag looks like it runs on port 80. Might be that port 80 is restricted (or in use), so docker desktop can't bind it. Maybe forward a random port to it.

You can also inspect the container. It will show env vars, networking binds, volume binds etc.
Make sure they align with what's in the official docker-compose. Once you get that working, you can start tweaking towards your requirement.