wietsedv/calibre-server repository overview

⁠Docker Calibre Server⁠

Automatically updating Docker image for calibre-server. The image contains a minimal Calibre⁠ installation and starts a Calibre server. The current version should correspond with the latest Calibre release⁠.

Note: This image is unofficial and not affiliated with Calibre.

⁠Usage

Calibre server is a REST API + web interface for Calibre. For more information about usage of calibre-server itself, refer to the user guide⁠ and the CLI manual⁠ of Calibre.

⁠Use case 1: Standalone container for local use

$ docker run -ti -p 8080:8080 wietsedv/calibre-server -v /path/to/library:/library

Now you have read+write access to your library via localhost:8080.

⁠Use case 2: Access from other containers within network

The command of "Use case 1" gives r+w access to your library on the host machine, but other containers in the network have readonly access. Calibre does not allow giving global r+w access without whitelisting or authentication. To give write access to other containers you should use the Docker host network type (not recommended) or you can whitelist containers within the bridge network:

$ docker run -ti -p 8080:8080 -v /path/to/library:/library -e TRUSTED_HOSTS="web1 web2" wietsedv/calibre-server

Note: IP addresses of whitelisted containers (web1 and web2) are resolved when calibre-server starts. So containers that need to access calibre-server have to start before calibre-server.

⁠Use case 3: Docker compose (recommended)

You can get the same setup as "Use case 2" with this docker-compose.yaml:

services:
    calibre:
        image: wietsedv/calibre-server
        volumes:
            - /path/to/library:/library
        ports: 
            - "8080:8080"
        depends_on:  # start web1 and web2 before calibre
            - web1
            - web2
        environment:
            TRUSTED_HOSTS: web1 web2  # whitelist web1 and web2
    
    web1:
        image: nginx:alpine

    web2:
        image: nginx:alpine