How/Why does Calibre on Synology Docker use port 3000?

LSIO Discussion Container Support
1

I was setting up a new container that natively uses port 3000 when I discovered port 3000 was in use by Calibre. I don’t explicitly set 3000. I am running Calibre 8.1.1 on a Synology SAN Server DSM 7.2.2.

Obviously I could explicitly map 3000 to something else. How does Calibre use ports 3000-3001?

 docker ps | grep 3000

156cf115e55c lscr.io/linuxserver/calibre:latest"/init" 19 hours ago Up 19 hours 0.0.0.0:8080-8081->8080-8081/tcp, :::8080-8081->8080-8081/tcp, 3000-3001/tcp, 0.0.0.0:8181->8181/tcp, :::8181->8181/tcp calibre 

services:
    calibre:
        container_name: calibre
        environment:
            - PUID=1026
            - PGID=100
            - TZ=Etc/UTC
        security_opt:
            - seccomp:unconfined #optional
        ports:
            - '8080:8080'
            - '8181:8181'
            - '8081:8081'
        volumes:
            - '/volume1/data/calibre/config:/config'
            - '/volume1/public/epub:/storage'
        restart: unless-stopped
        image: 'lscr.io/linuxserver/calibre:latest'
2

it’s for kasmvnc, if you don’t map it, it can’t be accessed outside of your custom bridge.
covered pretty thoroughly in the container readme…

3

Thanks - I now see the statement: This container is based on Docker Baseimage KasmVNC⁠ which means there are additional environment variables and run configurations to enable or disable specific functionality.

4

This topic was automatically closed 5 days after the last reply. New replies are no longer allowed.