Self-host Mylar3 with Levelrail

An automated comic book downloader that watches your series, finds new issues through your indexers and download client, and renames them into a library. GPL-3.0 licensed. Open the web UI, then add your indexers and download client under Configuration.

  • Authormylar3
  • LicenceGPL-3.0
  • Memory256 MiB
  • Archarm64
  • Services1

How to self-host Mylar3

  1. Pull the images

    One image is pulled on your server.

    Show images
    • lscr.io/linuxserver/mylar3:0.8.3
  2. Create the app

    One service starts in a single Compose app, with 3 named volume mounts for your data, on port 8090.

  3. Fill in the secrets

    3 settings are preset, you do not have to fill in anything.

  4. Open it

    Without a domain the app gets an sslip.io address; add --domain SERVICE=HOST to use your own.

Mylar3 requirements

Memory
About 256 MiB
Architectures
amd64 image published, arm64 image published
Ports
8090
Domain
Optional, an sslip.io address is used without one
Settings
none to fill in
License
GPL-3.0, copyleft license
  • Listed. It is in the catalog but not verified. Back up the data volume before changing an image tag.

Install Levelrail first

On a server with Levelrail running, run the command above, or open the dashboard: Apps, New app, Browse templates, then Mylar3. New to Levelrail? Install it on a fresh VPS first.

docker pull ghcr.io/glincker/levelrail:latest

Then levelrail-cli login --device. See Getting started and the Mylar3 docs page.

Deploy Mylar3 your way

Every format below deploys the same pinned images. Pick the one that fits how you work.

Deploy Mylar3 from the CLI

Add --domain SERVICE=HOST to serve a service on your own domain, for example --domain mylar3=app.example.com.

levelrail-cli templates install mylar3 --name my-mylar3

Deploy Mylar3 with the API

Create a token in the dashboard first. Name, env and domains are the request fields.

curl -X POST -H "Authorization: Bearer $TOKEN" -H "Content-Type: application/json" \
  https://levelrail.example.com/api/v1/service-templates/mylar3/install \
  -d '{
    "name": "my-mylar3"
  }'

Mylar3 configuration

Mylar3 services

ServiceImagePortsVolumes
mylar3 lscr.io/linuxserver/mylar3:0.8.3 8090 config -> /configcomics -> /comicsdownloads -> /downloads

Mylar3 environment variables

VariableServiceValue
PGID mylar3 Preset by the template
PUID mylar3 Preset by the template
TZ mylar3 Preset by the template

Ports and volumes

Ports
8090
Volumes
3 named mounts: config -> /config, comics -> /comics, downloads -> /downloads

Mylar3 FAQ

How much memory does Mylar3 need?

The catalog lists about 256 MiB of memory for Mylar3.

Does Mylar3 run on arm64?

For Mylar3, an arm64 image is published; amd64 is image published.

What licence is Mylar3 under?

Mylar3 is licensed under GPL-3.0, which is copyleft, so changes you distribute must be shared under the same terms.

Does Mylar3 need configuration before it starts?

No. The template fills in its own defaults.

Which ports does Mylar3 use?

Mylar3 listens on port 8090 inside the stack.

Where does Mylar3 keep its data?

In named volumes: config mounted at /config, comics mounted at /comics and downloads mounted at /downloads.

Can I deploy Mylar3 on Dokploy or Dokku?

The services and pinned images on this page can be run on any Docker host. The public Dokploy templates list we compared does not have an entry with the same id for Mylar3, so on Dokploy you would use a Docker Compose application with the file from this page. Dokku deploys container images with its own commands, so the pinned image lscr.io/linuxserver/mylar3:0.8.3 is what you deploy there.

levelrail-cli templates install mylar3 --name my-mylar3