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.
I use it for scripts or for esoteric error messages or problems I'm having in my dev environment.
I can't be bothered to understand a specific error message that I've never seen before because of an update or whatever.
So getting it to explain errors to me is handy.
I always review the LLMs process and the resulting changes it suggests (including searching what it's done if I don't get it).
It's essentially a context-aware search engine.
Actual coding and problem solving? I enjoy that.
Yeh, why not make billing able to carry ages verification?
Banks have to verify their customers. They (mostly) have a history of handling data well, it's in their interest/requirement to continue doing that.
The banking sector is well regulated compared to software/startups.
That can remove a large amount of service providers suddenly needing age verification. Just rely on the service purchase to verify it
Nah, it's never a DNS problem.
All official reporting indicates a well mannered race between candidates.
The correct and best leader has been chosen fairly by all citizens.
And all opponents now also agree, as do their voters.
"snorkel lenses" look ridiculous on large projectors.
https://epson.com/Accessories/Projector-Accessories/ELPLX02-Ultra-Short-throw-Lens/p/V12H004X02
Goes in the front like a normal lens, shoots backwards like a cursed lens.
The problem with short-throw lenses is that they will exacerbate any geometry issues. So aligning them is hard. And ANY tiny little non-planer issue with the screen surface gets massively multiplied.
You can get away with a lot of issues using long lenses. Short lenses are a pain.
ETA:
Linked is a 0.35 ratio lense.
So for every 0.35m from the screen, it will project a 1m wide screen.
0.7m away? 2m screen.
1.25m away? 5m wide screen.
3.5m away? 10m wide screen.
Nope, it's all DC. The voltage still alternates. They have to run alternating loads to compensate.
It's actually Teams Copilot for Office now
So Russia is using point-to-point radio.
Musk runs a service that gives internet everywhere and has the ability to pinpoint the ground access point precisely, as well as requiring a billing account to access.
You can't use starlink without the service provider knowing.
You can use cheap, 2nd hand, outdated, whatever network equipment to create your own local network without anyone knowing. It can be entirely airgapped and still work.
Unifi/Ubiquiti point to point radio kit is extremely easy to get hold of an can be used entirely airgapped (because it's on the border of pro & consumer level kit).
That's like saying "Russia is using ethernet cables" or "Russia found to be using intel NICs" or "Russia found to be using Mellanox SFP modules".
That can't be restricted.
The ability to tune in a point to point wireless network and maintain that ALL the way to the frontline takes skills. Any mid station can be targeted and isolate a bunch of frontline networks. Running multipath redundancy links is a significant challenge.
The ability to drop something on the ground and have instant internet access anywhere (starlink) is not a skill. It's an enabler, and musk enabled.
What's your vector, Victor?