Wallabag docker image

Dear Linuxserver.io team,

thanks a lot for your work creating and maintaining these docker images! Great job!

I would like to ask if it is possible to create a docker container for Wallabag?

Wallabag does offer a docker image but it is (as far as I can see, noob here) not compatible with armhf or having issues to connect to your mariadb container.

Furthermore, your expertise could be very usefule for making it work in a subfolder, what has never worked for me eventhough there are people out there claiming that it does.

Thanks again for your work and considering this request!

8 Likes

I would love to see linuxserver/wallabag

3 Likes

I would also appreciate an ARM supporting linuxserver/wallabag docker image.

Yes! I’ve been looking for a good bookmark/read-it-later manager for a while.

omg I came all the way to this forum today just to request JUST THIS!

Wallabag is awesome but the containers availible for it are awful.
The official wallabag container for example has to be run as ROOT which is really bad security wise… They do not offer any PUID/GUID arguments whatsoever… Not supported.

Please linuxserver this is a popular and very useful container… If you guys get this working I will amke big donations next payday :slight_smile:

Another vote for this! The official containers are an absolute pain.

another upvote here!

Same here! Can’t wait to use a solution from you guys!

Unfortunately, unless someone sends a pull request implementing support for base url/subfolder, for now the closest alternative we have is running wallabag under a subdomain, (e.g. wallabag.example.com).

Regarding the armhf docker image, it is possible to build it yourself on an armhf machine; for example with:

git clone https://github.com/wallabag/docker.git wallabag
cd wallabag && docker build --tag wallabag:localbuild .

Then simply run the image with the usual command:

docker run -p 80:80 wallabag:localbuild

Also would love to see this!

+1
I’m struggling to use the current docker wallabag with external db (mariadb on synology)

Don’t mean to necro post but I recently struggled with this and have a working solution with SWAG. If you don’t put wallabag in your compose file with swag and other LSIO containers, you need to make sure to have it connect to the network that SWAG is on like this:

networks:
  default:
    external:
      name: <the name of the SWAG network>

More detailed information is on my blog for the curious.
Here is my compose file:

version: '3'
services:
  wallabag:
    image: ikaruswill/wallabag:2.4.2
    container_name: wallabag
    environment:
      - MYSQL_ROOT_PASSWORD=wallaroot
      - SYMFONY__ENV__DATABASE_DRIVER=pdo_mysql
      - SYMFONY__ENV__DATABASE_HOST=walla_db
      - SYMFONY__ENV__DATABASE_PORT=3306
      - SYMFONY__ENV__DATABASE_NAME=wallabag
      - SYMFONY__ENV__DATABASE_USER=wallabag
      - SYMFONY__ENV__DATABASE_PASSWORD=wallapass
      - SYMFONY__ENV__DATABASE_CHARSET=utf8mb4
      - SYMFONY__ENV__MAILER_HOST=127.0.0.1
      - SYMFONY__ENV__MAILER_USER=~
      - SYMFONY__ENV__MAILER_PASSWORD=~
      - SYMFONY__ENV__FROM_EMAIL=wallabag@example.com
      - SYMFONY__ENV__DOMAIN_NAME=https://YOURCUSTOMDOMAIN.com #If using a local host, put your IP and port number in here. If using a reverse proxy, you will need to put in your external port number. 10.10.0.4:80. If you aren't using ssl, then use http://
      - SYMFONY__ENV__SERVER_NAME="Pi Information Station"
      - SYMFONY__ENV__FOSUSER_CONFIRMATION=FALSE
    ports:
      - "8080:80" #i am using LSIO SWAG so my external port is 8080 but you can use any value. If you have no other services using port 80, then 80:80 can be used.
    volumes:
      - /path/where/you/save_data/images:/var/www/wallabag/web/assets/images
  walla_db:
    image: mariadb
    environment:
      - MYSQL_ROOT_PASSWORD=wallaroot
    volumes:
      - /path/where/you/save_data/data:/var/lib/mysql
  redis:
    image: redis:alpine