The LinuxServer.io team brings you another container release featuring easy user mapping and community support. Find us for support at:

• forum.linuxserver.io
• IRC on freenode at #linuxserver.io
• Podcast covers everything to do with getting the most from your Linux Server plus a focus on all things Docker and containerisation!

linuxserver/ubooquity

Ubooquity is a free, lightweight and easy-to-use home server for your comics and ebooks. Use it to access your files from anywhere, with a tablet, an e-reader, a phone or a computer.

Usage

docker create \
  --name=ubooquity \
  -v <path to data>:/config \
  -v <path to books>:/books \
  -v <path to comics>:/comics \
  -v <path to raw files>:/files \
  -e MAXMEM=<maxmem> \
  -e PGID=<gid> -e PUID=<uid>  \
  -p 2202:2202 \
  -p 2203:2203 \
  linuxserver/ubooquity

Parameters

The parameters are split into two halves, separated by a colon, the left hand side representing the host and the right the container side. For example with a port -p external:internal - what this shows is the port mapping from internal to external of the container. So -p 8080:80 would expose port 80 from inside the container to be accessible from the host's IP on port 8080 http://192.168.x.x:8080 would show you what's running INSIDE the container on port 80.

• -p 2202 - the library port
• -p 2203 - the admin port
• -v /config - Config files and database for ubooquity
• -v /books - Location of books.
• -v /comics - Location of comics.
• -v /files - Location of raw files.
• -e MAXMEM - to set the maximum memory
• -e PGID for GroupID - see below for explanation
• -e PUID for UserID - see below for explanation

It is based on alpine linux with s6 overlay, for shell access whilst the container is running do docker exec -it ubooquity /bin/bash.

MAXMEM

The quantity of memory allocated to Ubooquity depends on the hardware your are running it on. If this quantity is too small, you might sometime saturate it with when performing memory intensive operations. That’s when you get java.lang.OutOfMemoryError: Java heap space errors.

You can explicitly set the amount of memory Ubooquity is allowed to use (be careful to set a value lower than the actual physical memory of your hardware).

If no value is set it will default to 512MB.

User / Group Identifiers

Sometimes when using data volumes (-v flags) permissions issues can arise between the host OS and the container. We avoid this issue by allowing you to specify the user PUID and group PGID. Ensure the data volume directory on the host is owned by the same user you specify and it will "just work" ™.

In this instance PUID=1001 and PGID=1001. To find yours use id user as below:

  $ id <dockeruser>
    uid=1001(dockeruser) gid=1001(dockergroup) groups=1001(dockergroup)

Setting up the application

IMPORTANT Ubooquity has now been upgraded to version 2 and for existing v1.x users we recommend cleaning your appdata and reinstalling, due to changes in the application itself making the two versions essentially incompatible with each other. Also the admin page and library pages are now on separate ports as detailed below.

Access the admin page at http://<your-ip>:2203/ubooquity/admin/ and set a password.

Then you can access the webui at http://<your-ip>:2202/ubooquity/

This container will automatically scan your files at startup.

Info

• Shell access whilst the container is running: docker exec -it ubooquity /bin/bash

• To monitor the logs of the container in realtime: docker logs -f ubooquity

• container version number

docker inspect -f '{{ index .Config.Labels "build_version" }}' ubooquity

• image version number

docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/ubooquity

Versions

• 16.07.17: Upgrade to Ubooquity 2.1.0, see setting up application section for important info for existing v1.x users.
• 26.05.17: Rebase to alpine 3.6.
• 08.04.17: Switch to java from 3.5 repo, fixes login crashes.
• 06.02.17: Rebase to alpine 3.5.
• 06.12.16: Initial Release.