Update: I’ve gone back to standard docker-compose. It’s actually easier for me than Docker Desktop. Thanks all for the helpful suggestions.
Due to persistent brain fog lately, I opted for Docker Desktop on this machine. I chose the image from doc75/wallabag:prev-prod and ran it. But I can’t access it from the frontend.
I’d rather get it going through Docker Desktop rather than the usual docker compose via terminal. Can anyone help?
Logs, as requested:
[OK] Cache for the "prod" environment (debug=false) was successfully cleared.
Trying to install assets as relative symbolic links.
--- ------------------------ ------------------
Bundle Method / Error
--- ------------------------ ------------------
✔ NelmioApiDocBundle relative symlink
✔ CraueConfigBundle relative symlink
✔ BabDevPagerfantaBundle relative symlink
✔ FOSJsRoutingBundle relative symlink
--- ------------------------ ------------------
[OK] All assets were successfully installed.
wallabag is ready!
::1 - - [26/Feb/2026:20:23:52 +0000] "GET /api/info HTTP/1.1" 200 81 "-" "healthcheck"
Package php-http/message-factory is abandoned, you should avoid using it. Use psr/http-factory instead.
Package scheb/2fa-qr-code is abandoned, you should avoid using it. No replacement was suggested.
Package sensio/framework-extra-bundle is abandoned, you should avoid using it. Use Symfony instead.
Package symfony/debug is abandoned, you should avoid using it. Use symfony/error-handler instead.
Package symfony/inflector is abandoned, you should avoid using it. Use EnglishInflector from the String component instead.
Package wallabag/php-mobi is abandoned, you should avoid using it. No replacement was suggested.
Package php-cs-fixer/diff is abandoned, you should avoid using it. No replacement was suggested.
Package symfony/web-server-bundle is abandoned, you should avoid using it. No replacement was suggested.
Generating optimized autoload files
101 packages you are using are looking for funding.
Use the `composer fund` command to find out more!
> Incenteev\ParameterHandler\ScriptHandler::buildParameters
> bin/console cache:clear --no-warmup
> bin/console assets:install web --symlink --relative
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)
Thanks. I’ll go the docker-compose route after all. Familiarity might be better than whatever conveniences Docker Desktop offers. I really appreciate the help. I have a proper docker-compose.yml file now at least so I should be able to work from there.
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.
I’m confused too. I’m not sure what it’s offering. But I have the container running now and can access it from the browser.
I’m on macOS (will be migrating back to Linux in the future) and had to install something called Colima too, via brew, to allow docker itself to run. But it’s a service and once it’s started, it starts at login. So, I can forget about it and focus on docker. I’m very happy.
My Pi3B is struggling to run the services I have on it so I couldn’t add another container there. Thanks again, I can finally organise information better and hopefully contribute to better online discourse hopefully!