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.
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/73819697Describes 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)