This post follows on from Part 1 of my issues getting Wallabag self-hosted using Docker. Previously I had problems getting the Wallabag container to talk to the database successfully, so check out the previous post if that is the problem you are having. Having made everything talk happily to one another I thought I was finished, but no. The following day I found that the wallabag docker image was not running, I couldn’t post any articles to it.

In this post I am going to go over the problems I had trying to get Wallabag running on Docker connected to a MariaDB instance. Why am I doing this? There are quite a few guides on the web that show how simple this was, but as you may have guessed, it wasn’t that simple for me. What is Wallabag Wallabag is an app that saves webpages for reading later. If you have ever used or heard of ReadItLater or Pocket, then you know the type of thing.

I was having some problems uploading photos from my phone to the instance of Nextcloud I have running on my local server, so after checking all the obvious stuff; server was running, tailscale was working (another post on this to come shortly) I checked for updates on both the Android app and the docker image. This is when things went horribly wrong! The Android app was upto date, but there was a newer docker image, so I restarted the docker container, it dutifully downloaded, then I was greeted with the following:

Download and install Visual Studio Community Edition When running the installer it will ask which components are required, the only one you have to choose for Jellyfin development is .NET Desktop Development: The install will be close to 6GB so may take a while. While it is installing you can install FFMpeg, this isn’t technically required to get Jellyfin to run whilst you develop, for example if you are only working on a metadata plugin you won’t need the server to transcode anything, but if you do need make sure items play then it is best to install FFMpeg.