gazee
Container
A WebApp Comic Reader for your favorite digital comics. Reach and read your comic library from any web connected device with a modern web browser
Image details
Configuration
TypeContainerlinuxlinuxserver/gazee:latest4242/tcp/config/comics/mylarPUID=1000PGID=1000Template by dnburgess
Standalone Install
Select an install method, to see config/commands for deploying gazee
Install on Portainer
Import all app templates into your Portainer instance, for easy 1-click deploys
- Ensure both Docker and Portainer are installed, and up-to-date
- Log into your Portainer web UI
- Under Settings → App Templates, paste the below URL
- Head to Home → App Templates, and the list of apps will show up
- Select gazee, fill in any config options, and hit Deploy
Template Import URL
https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json
Show Me
More install options in our documentation.

The LinuxServer.io team brings you another container release featuring :-
regular and timely application updates easy user mappings (PGID, PUID) custom base image with s6 overlay weekly base OS updates with common layers across the entire LinuxServer.io ecosystem to minimise space usage, down time and bandwidth regular security updates
Find us at:
- Discord - realtime support / chat with the community and the team.
- IRC - on freenode at
#linuxserver.io. Our primary support channel is Discord. - Blog - all the things you can do with our containers including How-To guides, opinions and much more!
linuxserver/gazee
THIS IMAGE IS DEPRECATED, IT WILL NO LONGER RECEIVE UPDATES. Gazee is a WebApp Comic Reader for your favorite digital comics. Reach and read your comic library from any web connected device with a modern web browser.

Supported Architectures
Our images support multiple architectures such asx86-64, arm64 and armhf. We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here. Simply pulling
linuxserver/gazee should retrieve the correct image for your arch, but you can also pull specific arch images via tags.The architectures supported by this image are:
| Architecture | Tag |
|---|---|
| x86-64 | amd64-latest |
| arm64 | arm64v8-latest |
| armhf | arm32v6-latest |
Usage
Here are some example snippets to help you get started creating a container.docker
docker create \
--name=gazee \
-e PUID=1000 \
-e PGID=1000 \
-p 4242:4242 \
-v /path/to/appdata/config:/config \
-v path to comics:/comics \
-v path to mylar data:/mylar \
-v path to SSL certs:/certs \
--restart unless-stopped \
linuxserver/gazeedocker-compose
Compatible with docker-compose v2 schemas.```
version: "2" services: gazee:image: linuxserver/gazee
container_name: gazee
environment:
- PUID=1000
- PGID=1000
volumes:
- /path/to/appdata/config:/config
- path to comics:/comics
- path to mylar data:/mylar
- path to SSL certs:/certs
ports:
- 4242:4242
restart: unless-stopped## Parameters
Container images are configured using parameters passed at runtime (such as those above). These parameters are separated by a colon and indicate `external:internal` respectively. For example, `-p 8080:80` would expose port `80` from inside the container to be accessible from the host's IP on port `8080` outside the container.
<table><thead><tr><th>Parameter</th><th>Function</th></tr></thead><tbody><tr><td><code>-p 4242</code></td><td>WebUI</td></tr><tr><td><code>-e PUID=1000</code></td><td>for UserID - see below for explanation</td></tr><tr><td><code>-e PGID=1000</code></td><td>for GroupID - see below for explanation</td></tr><tr><td><code>-v /config</code></td><td>Where Gazee should store config files.</td></tr><tr><td><code>-v /comics</code></td><td>Path to comics folder.</td></tr><tr><td><code>-v /mylar</code></td><td>Path to Mylar DB.</td></tr><tr><td><code>-v /certs</code></td><td>Where SSL certs should be stored.</td></tr></tbody></table>
## User / Group Identifiers
When using 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 any volume directories on the host are owned by the same user you specify and any permissions issues will vanish like magic.
In this instance `PUID=1000` and `PGID=1000`, to find yours use `id user` as below:
$ id usernameuid=1000(dockeruser) gid=1000(dockergroup) groups=1000(dockergroup)
## Application Setup
Webui can be found at `your-ip:4242`
Default username and password for the web interface:
* **Username:** `admin`
* **Password:** `gazee`
Click the gear icon to go to the settings page.
Change the default admin password or add a new admin and remove the admin user altogether.
Comic path should be set to `/comics`
*Optional* Mylar DB path should be set to `/mylar`
*Optional* path for certificates and keys should be set to `/certs`
After you update the settings, Gazee will restart and begin an intial scan of your comic library.
Happy Reading!
## Support Info
* Shell access whilst the container is running: `docker exec -it gazee /bin/bash`
* To monitor the logs of the container in realtime: `docker logs -f gazee`
* container version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' gazee`
* image version number
* `docker inspect -f '{{ index .Config.Labels "build_version" }}' linuxserver/gazee`
## Updating Info
Most of our images are static, versioned, and require an image update and container recreation to update the app inside. With some exceptions (ie. nextcloud, plex), we do not recommend or support updating apps inside the container. Please consult the [Application Setup](#application-setup) section above to see if it is recommended for the image.
Below are the instructions for updating containers:
### Via Docker Run/Create
* Update the image: `docker pull linuxserver/gazee`
* Stop the running container: `docker stop gazee`
* Delete the container: `docker rm gazee`
* Recreate a new container with the same docker create parameters as instructed above (if mapped correctly to a host folder, your `/config` folder and settings will be preserved)
* Start the new container: `docker start gazee`
* You can also remove the old dangling images: `docker image prune`
### Via Docker Compose
* Update all images: `docker-compose pull`
* or update a single image: `docker-compose pull gazee`
* Let compose update all containers as necessary: `docker-compose up -d`
* or update a single container: `docker-compose up -d gazee`
* You can also remove the old dangling images: `docker image prune`
### Via Watchtower auto-updater (especially useful if you don't remember the original parameters)
* Pull the latest image at its tag and replace it with the same env variables in one run:
```
docker run --rm \
-v /var/run/docker.sock:/var/run/docker.sock \
containrrr/watchtower \
--run-once gazee
```
* You can also remove the old dangling images: `docker image prune`
## Building locally
If you want to make local modifications to these images for development purposes or just to customize the logic:
git clone https://github.com/linuxserver/docker-gazee.git
cd docker-gazee
docker build \
--no-cache \
--pull \
-t linuxserver/gazee:latest .
The ARM variants can be built on x86_64 hardware using `multiarch/qemu-user-static`
docker run --rm --privileged multiarch/qemu-user-static:register --reset
```Once registered you can define the dockerfile to use with
-f Dockerfile.aarch64.Versions
- 27.03.19: - Deprecate image and get in semi working state.
- 11.02.19: - Add pipeline logic and multi arch.
- 17.08.18: - Rebase to alpine 3.8.
- 30.12.17: - Ensure version 11 of cherrypy.
- 07.12.17: - Initial Release.
Serve gazee 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 gazee.example.com to http://gazee:4242
Add this to your Caddyfile
gazee.example.com {
reverse_proxy http://gazee:4242
}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:
137means killed, usually out of memory.126or127means the command inside the image is broken.
Published on a random port
This template exposes 4242/tcp without setting a host port,
so Docker picks a random free one on every deploy.
- Find it in the Ports column of Portainer's container list, or with
docker port <container>
Image won't pull
Test the pull directly on the host: docker pull linuxserver/gazee: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 loginto 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, arm, arm64/v8 - Check yours with
uname -m: x86_64 is amd64, aarch64 is arm64. Raspberry Pi and other ARM boards are the usual culprits.
Raise an issue
Found something which isn't working as it should? Here's how to report it.
- Bug within the app: Open an issue within the app's repo
- Template not working: Open an issue on dnburgess/self-hosted-template
- This website not working: Open an issue on lissy93/portainer-templates
A single container
gazee runs as one container, the simplest kind of app here. Just the one image to pull and nothing else wired up alongside it.
The app image
An image is the app packed up ready to go, everything gazee needs bundled into one download. This template pulls linuxserver/gazee:latest, which Docker fetches once (about 48 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. gazee's comes from Docker Hub, published by linuxserver.
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. 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, arm, arm64/v8, 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. Here the app exposes a port but leaves the host side blank, so Docker picks a free one for you. It opens:
4242, published on a random host port
Volumes
A volume is where gazee 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:
/configas a volume Docker manages for you/comicsas a volume Docker manages for you/mylaras a volume Docker manages for you
Environment variables
Environment variables are the settings you hand over when you deploy, things like a password or a timezone. gazee takes 2 of them, all with defaults you can leave alone or tweak:
PUID, defaults to1000PGID, defaults to1000
Users and permissions
The PUID and PGID settings tell it which user and group to act as on your host. Point them at your own account (find yours with id $USER) so the files it writes into your mounted folders come out owned by you rather than root.
Networking
Nothing custom is set, so gazee sits on Docker's default bridge network: its own private space that reaches the outside world only through the ports it publishes.
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 gazee up. Add the template list to Portainer once, then deploying gazee is a click rather than a wall of config.