Portainer Templates logo

Portainer Templates

Kapowarr

Stack

EbooksComics

Kapowarr is a software to build and manage a comic book library, fitting in the arr suite of software.

Image details

Pulls: 2.9M
Architecture: amd64, arm64
Image size: 60 MB
Latest: v1.3.1
User: mrcas
Created: May 24, 2023
Updated: 4 months ago
Status: active

Configuration

Type
Compose
Platform
linux
Image
mrcas/kapowarr:latest
Ports
5656:5656
Volumes
/app/db : /portainer/Files/AppData/Config/kapowarr-db/app/temp_downloads : /portainer/comics/downloads/content : /portainer/comics/kapowarr
Source
Repo

Template by xneo1·Source

Standalone Install

Select an install method, to see config/commands for deploying Kapowarr

Installation method

Install on Portainer

Import all app templates into your Portainer instance, for easy 1-click deploys

  1. Ensure both Docker and Portainer are installed, and up-to-date
  2. Log into your Portainer web UI
  3. Under Settings → App Templates, paste the below URL
  4. Head to Home → App Templates, and the list of apps will show up
  5. Select Kapowarr, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me demo
Original stackfile

The compose file this template deploys, straight from its repo:

services:
    kapowarr:
        container_name: kapowarr
        volumes:
            - /portainer/Files/AppData/Config/kapowarr-db:/app/db
            - /portainer/comics/downloads:/app/temp_downloads
            - /portainer/comics/kapowarr:/content
        ports:
            - 5656:5656
        image: mrcas/kapowarr:latest

Or deploy it directly from the source:

git clone https://github.com/xneo1/portainer_templates
cd portainer_templates
docker compose -f Template/Stack/kapowarr.yml up -d

More install options in our documentation.

Kapowarr

<a href="https://hub.docker.com/r/mrcas/kapowarr"><img src="https://img.shields.io/docker/pulls/mrcas/kapowarr?color=blue"></a>
<a href="https://github.com/Casvt/Kapowarr"><img src="https://img.shields.io/github/stars/Casvt/Kapowarr?style=flat&color=blue"></a>
<a href="https://ko-fi.com/casvt"><img src="https://img.shields.io/badge/Donate-Ko--Fi-blue"></a>
<a href="https://github.com/Casvt/Kapowarr/blob/main/LICENSE"><img src="https://img.shields.io/github/license/Casvt/Kapowarr?color=blue"></a>


Kapowarr is a software to build and manage a comic book library, fitting in the arr suite of software.
Kapowarr allows you to build a digital library of comics. You can add volumes, map them to a folder and start managing! Download, rename, move and convert issues of the volume (including TPBs, One Shots, Hard Covers, and more). The whole process is automated and can be customised in the settings.
Featured on Noted and Respectlytics.

Features

  • Run a "Search Monitored" to download whole volumes with one click
  • Or use "Manual Search" to decide yourself what to download
  • Import your existing library right into Kapowarr
  • Support for all major operating systems
  • Download using DDL, Pixeldrain, Mega and many other services
  • Downloaded files automatically get moved wherever you want and renamed in the format you desire
  • Archive files can be extracted and their contents renamed after downloading or with a single click
  • The recognisable UI from the arr suite of software

Installation, support and documentation

Screenshots

Serve Kapowarr on your own domain behind Caddy, Nginx or Traefik. Fill in your domain and copy the result. It's a starting point, some apps need their own base URL or extra headers set too.

Proxying kapowarr.example.com to http://kapowarr:5656

Add this to your Caddyfile

kapowarr.example.com {
	reverse_proxy http://kapowarr:5656
}

Check the logs first

Nine times out of ten the logs tell you exactly what went wrong.

  • In Portainer, go to Containers, click the container, then Logs. Or run docker logs <container>
  • Exit codes help too: 137 means killed, usually out of memory. 126 or 127 means the command inside the image is broken.

Port already in use

If deployment fails with "Bind for 0.0.0.0:5656 failed: port is already allocated", something else on your server is using that port.

  • Find what's using it: sudo ss -tlnp | grep :5656
  • Stop the other service, or pick a different host port. In 5656:5656 only the left number is yours to change, the right one belongs to the app.

Running but the page won't load

The container is up but nothing appears in your browser.

  • Use your server's real IP: http://your-server-ip:5656. The 0.0.0.0 link Portainer shows isn't a real address.
  • Give it a minute after first deploy, kapowarr can take a while to initialise.
  • Make sure your firewall allows the port, e.g. sudo ufw allow 5656

Permission denied on volumes

If the logs show "permission denied", the app can't write to its data folder on the host.

  • Fix the ownership: sudo chown -R 1000:1000 /portainer/Files/AppData/Config/kapowarr-db (and the same for the other mapped folders)

Image won't pull

Test the pull directly on the host: docker pull mrcas/kapowarr:latest

  • "manifest unknown" means the tag no longer exists. This template uses latest, so try pinning a specific version instead.
  • "toomanyrequests" is the Docker Hub rate limit. Log in with docker login to raise it.
  • "no space left on device" means a full disk. Reclaim space with docker system prune

"exec format error"

This means the image was built for a different CPU architecture than your server.

  • This image supports: amd64, arm64
  • Check yours with uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.

Stack won't deploy

Compose stacks fail fast on small mistakes, and Portainer shows the reason just above the editor.

  • YAML only accepts spaces for indentation, a single tab breaks the whole file.

Raise an issue

Found something which isn't working as it should? Here's how to report it.

A Compose stack

Kapowarr is a Compose stack, a set of containers defined in one file and brought up together by Portainer, then started and stopped as a single app.

The app image

An image is the app packed up ready to go, everything Kapowarr needs bundled into one download. This template pulls mrcas/kapowarr:latest, which Docker fetches once (about 60 MB) and then starts your own copy from.

Where the image comes from

Docker pulls its images from registries, public libraries of ready-built apps. Kapowarr's comes from Docker Hub, published by mrcas.

Version tags

The bit after the colon in the image name is the version tag. Here it's latest, which always points at the newest build, so a redeploy can bump you to a newer release without you asking. Newest right now is v1.3.1. Pin a specific tag if you would rather stay on one version.

Which machines it runs on

Every image is built for particular CPU types. This one ships for amd64, arm64, so it runs on both regular x86 servers and ARM boards like a Raspberry Pi.

Ports

A port is the door the app answers on. A mapping like 5656:5656 means it's reachable on port 5656 of your server, where the left number is yours to change and the right one belongs to the app. It opens:

  • 5656:5656

Volumes

A volume is where Kapowarr keeps its files so they survive an update or a restart. Without one, anything it saves would sit inside the container and vanish the moment it's recreated. This template mounts:

  • /app/db from /portainer/Files/AppData/Config/kapowarr-db on the host
  • /app/temp_downloads from /portainer/comics/downloads on the host
  • /content from /portainer/comics/kapowarr on the host

Networking

Nothing custom is set, so Kapowarr sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.

Container name

Once it's deployed, Portainer names the container kapowarr. That's what you'll spot in the containers list and use in commands like docker logs kapowarr.

Platform

The platform is linux, the kind of system the container is built to run on. Docker and Portainer handle this on a normal Linux server.

Portainer app templates

Zooming out, this whole page comes from a Portainer app template: a short recipe telling Portainer how to set Kapowarr up. Add the template list to Portainer once, then deploying Kapowarr is a click rather than a wall of config.