Kometa

Kometa is a powerful tool designed to give you complete control over your media libraries. With Kometa, you can take your customization to the next level, with granular control over metadata, collections, overlays, and much more.

Image details

Pulls: 1.2M

Architectures: amd64, arm64

Image size: 294 MB

Latest: 2.4.4

User: linuxserverci

Created: Apr 23, 2024

Updated: 2 days ago

Status: active

Source details

Repo: Kometa-Team/Kometa

Stars: 3k

Forks: 371

Language: Python

License: MIT

Latest: v2.4.4 · 25 days ago

Updated: 1 hour ago

Website: kometa.wiki/

Configuration

Type

Container

Platform

linux

Image

linuxserver/kometa:latest

Ports

80:80/tcp

Volumes

/config : /srv/lsio/kometa/config

Env vars

PUID=1000PGID=1000TZ=Etc/UTCKOMETA_CONFIG=/config/config.ymlKOMETA_TIMES=03:00KOMETA_RUN=FalseKOMETA_TESTS=FalseKOMETA_NO_MISSING=False

Restart

unless-stopped

Template by technorabilia

Notes

Portainer App Templates by Technorabilia, based on data provided by LinuxServer.io.

Ensure to create the following volume directories on the host file system, or modify the paths in the volume mapping section under the advanced options below, as needed.

mkdir -p /srv/lsio/kometa/config

Installation

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 the app you wish to deploy, fill in any config options, and hit Deploy

Template Import URL

https://raw.githubusercontent.com/Lissy93/portainer-templates/main/templates.json

Show Me

docker run -d --name Kometa \
  -p 80:80/tcp \
  -e 'PUID=1000' \
  -e 'PGID=1000' \
  -e 'TZ=Etc/UTC' \
  -e 'KOMETA_CONFIG=/config/config.yml' \
  -e 'KOMETA_TIMES=03:00' \
  -e 'KOMETA_RUN=False' \
  -e 'KOMETA_TESTS=False' \
  -e 'KOMETA_NO_MISSING=False' \
  -v /srv/lsio/kometa/config:/config \
  --restart=unless-stopped \
  linuxserver/kometa:latest

Save this file as compose.yaml and run docker compose up -d
Use this only as a guide.

services:
  kometa:
    image: linuxserver/kometa:latest
    ports:
      - 80:80/tcp
    volumes:
      - /srv/lsio/kometa/config:/config
    environment:
      PUID: '1000'
      PGID: '1000'
      TZ: Etc/UTC
      KOMETA_CONFIG: /config/config.yml
      KOMETA_TIMES: '03:00'
      KOMETA_RUN: 'False'
      KOMETA_TESTS: 'False'
      KOMETA_NO_MISSING: 'False'
    restart: unless-stopped

Save this file as kometa-stack.yml, then from a manager node, run docker stack deploy -c kometa-stack.yml kometa

version: '3.8'
services:
  kometa:
    image: linuxserver/kometa:latest
    ports:
      - 80:80/tcp
    volumes:
      - /srv/lsio/kometa/config:/config
    environment:
      PUID: '1000'
      PGID: '1000'
      TZ: Etc/UTC
      KOMETA_CONFIG: /config/config.yml
      KOMETA_TIMES: '03:00'
      KOMETA_RUN: 'False'
      KOMETA_TESTS: 'False'
      KOMETA_NO_MISSING: 'False'
    deploy:
      restart_policy:
        condition: any

Save each file below into a folder, then run kubectl apply -f .
Written for k3s, but works on any cluster: bind mounts use hostPath, named volumes get a persistent volume claim, and ports are exposed via a LoadBalancer service.

`kometa-deployment.yaml`

apiVersion: apps/v1
kind: Deployment
metadata:
  name: kometa
  labels:
    app: kometa
spec:
  replicas: 1
  selector:
    matchLabels:
      app: kometa
  template:
    metadata:
      labels:
        app: kometa
    spec:
      containers:
        - name: kometa
          image: linuxserver/kometa:latest
          env:
            - name: PUID
              value: '1000'
            - name: PGID
              value: '1000'
            - name: TZ
              value: Etc/UTC
            - name: KOMETA_CONFIG
              value: /config/config.yml
            - name: KOMETA_TIMES
              value: '03:00'
            - name: KOMETA_RUN
              value: 'False'
            - name: KOMETA_TESTS
              value: 'False'
            - name: KOMETA_NO_MISSING
              value: 'False'
          ports:
            - containerPort: 80
              protocol: TCP
          volumeMounts:
            - name: kometa-data-0
              mountPath: /config
      volumes:
        - name: kometa-data-0
          hostPath:
            path: /srv/lsio/kometa/config

`kometa-service.yaml`

apiVersion: v1
kind: Service
metadata:
  name: kometa
spec:
  type: LoadBalancer
  selector:
    app: kometa
  ports:
    - name: 80-tcp
      port: 80
      targetPort: 80
      protocol: TCP

Save this file as ~/.config/containers/systemd/kometa.container

[Unit]
Description=Kometa

[Container]
Image=linuxserver/kometa:latest
ContainerName=kometa
PublishPort=80:80/tcp
Environment=PUID=1000
Environment=PGID=1000
Environment=TZ=Etc/UTC
Environment=KOMETA_CONFIG=/config/config.yml
Environment=KOMETA_TIMES=03:00
Environment=KOMETA_RUN=False
Environment=KOMETA_TESTS=False
Environment=KOMETA_NO_MISSING=False
Volume=/srv/lsio/kometa/config:/config

[Service]
Restart=always

[Install]
WantedBy=default.target

Then reload systemd and start the service:

systemctl --user daemon-reload
systemctl --user start kometa

For a system-wide service, use /etc/containers/systemd/ and drop --user.

For more installation options, see the Documentation in our GitHub repo

For app-specific guidance, check Kometa's own repo at Kometa-Team/Kometa

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:

Blog - all the things you can do with our containers including How-To guides, opinions and much more!
Discord - realtime support / chat with the community and the team.
Discourse - post on our community forum.
GitHub - view the source for all of our repositories.
Open Collective - please consider helping us by either donating or contributing to our budget

linuxserver/kometa

Supported Architectures

We utilise the docker manifest for multi-platform awareness. More information is available from docker here and our announcement here.
Simply pulling lscr.io/linuxserver/kometa:latest 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 | Available | Tag | | :----: | :----: | ---- | | x86-64 | ✅ | amd64-\ | | arm64 | ✅ | arm64v8-\ |

Version Tags

This image provides various versions that are available via tags. Please read the descriptions carefully and exercise caution when using unstable or development tags.
| Tag | Available | Description | | :----: | :----: |--- | | latest | ✅ | Stable releases. | | develop | ✅ | Latest commits from the develop branch | | nightly | ✅ | Latest commits from the nightly branch |

Application Setup

There is a walkthrough available to help get you up and running.
This image supports all of the environment variables listed here and all commandline arguments.
To perform a one-time run use docker run (or docker compose run) with the --rm, and -e KOMETA_RUN=True or --run arguments. This will cause the container to process your config immediately instead of waiting for the scheduled time, and delete the old container after completion.
For more information see the official wiki.

Usage

To help you get started creating a container from this image you can either use docker-compose or the docker cli.
>!NOTE >Unless a parameter is flagged as 'optional', it is mandatory and a value must be provided.

docker-compose (recommended, click here for more info)

---
services:
  kometa:
    image: lscr.io/linuxserver/kometa:latest
    container_name: kometa
    environment:
      - PUID=1000
      - PGID=1000
      - TZ=Etc/UTC
      - KOMETA_CONFIG=/config/config.yml #optional
      - KOMETA_TIMES=03:00 #optional
      - KOMETA_RUN=False #optional
      - KOMETA_TESTS=False #optional
      - KOMETA_NO_MISSING=False #optional
    volumes:
      - /path/to/kometa/config:/config
    restart: unless-stopped

docker cli (click here for more info)

docker run -d \
  --name=kometa \
  -e PUID=1000 \
  -e PGID=1000 \
  -e TZ=Etc/UTC \
  -e KOMETA_CONFIG=/config/config.yml `#optional` \
  -e KOMETA_TIMES=03:00 `#optional` \
  -e KOMETA_RUN=False `#optional` \
  -e KOMETA_TESTS=False `#optional` \
  -e KOMETA_NO_MISSING=False `#optional` \
  -v /path/to/kometa/config:/config \
  --restart unless-stopped \
  lscr.io/linuxserver/kometa:latest

Parameters

Containers 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.
| Parameter | Function | | :----: | --- | | -e PUID=1000 | for UserID - see below for explanation | | -e PGID=1000 | for GroupID - see below for explanation | | -e TZ=Etc/UTC | specify a timezone to use, see this list. | | -e KOMETA_CONFIG=/config/config.yml | Specify a custom config file to use. | | -e KOMETA_TIMES=03:00 | Comma-separated list of times to update each day. Format: HH:MM. | | -e KOMETA_RUN=False | Set to True to run without the scheduler. | | -e KOMETA_TESTS=False | Set to True to run in debug mode with only collections that have test: true. | | -e KOMETA_NO_MISSING=False | Set to True to run without any of the missing movie/show functions. | | -v /config | Persistent config files |

Environment variables from files (Docker secrets)

You can set any environment variable from a file by using a special prepend FILE__.
As an example:

-e FILE__MYVAR=/run/secrets/mysecretvariable

Will set the environment variable MYVAR based on the contents of the /run/secrets/mysecretvariable file.

Umask for running applications

For all of our images we provide the ability to override the default umask settings for services started within the containers using the optional -e UMASK=022 setting. Keep in mind umask is not chmod it subtracts from permissions based on it's value it does not add. Please read up here before asking for support.

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 your_user as below:

id your_user

Example output:

uid=1000(your_user) gid=1000(your_user) groups=1000(your_user)

Docker Mods

We publish various Docker Mods to enable additional functionality within the containers. The list of Mods available for this image (if any) as well as universal mods that can be applied to any one of our images can be accessed via the dynamic badges above.

Support Info

Shell access whilst the container is running:

```bash
docker exec -it kometa /bin/bash
```

To monitor the logs of the container in realtime:

```bash
docker logs -f kometa
```

Container version number:

```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' kometa
```

Image version number:

```bash
docker inspect -f '{{ index .Config.Labels "build_version" }}' lscr.io/linuxserver/kometa:latest
```

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 (noted in the relevant readme.md), we do not recommend or support updating apps inside the container. Please consult the Application Setup section above to see if it is recommended for the image.
Below are the instructions for updating containers:

Via Docker Compose

Update images:

* All images:

    ```bash
    docker-compose pull
    ```

* Single image:

    ```bash
    docker-compose pull kometa
    ```

Update containers:

* All containers:

    ```bash
    docker-compose up -d
    ```

* Single container:

    ```bash
    docker-compose up -d kometa
    ```

You can also remove the old dangling images:

```bash
docker image prune
```

Via Docker Run

Update the image:

```bash
docker pull lscr.io/linuxserver/kometa:latest
```

Stop the running container:

```bash
docker stop kometa
```

Delete the container:

```bash
docker rm kometa
```

Recreate a new container with the same docker run parameters as instructed above (if mapped correctly to a host folder, your /config folder and settings will be preserved)
You can also remove the old dangling images:

```bash
docker image prune
```

Image Update Notifications - Diun (Docker Image Update Notifier)

>!TIP >We recommend Diun for update notifications. Other tools that automatically update containers unattended are not recommended or supported.

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-kometa.git
cd docker-kometa
docker build \
  --no-cache \
  --pull \
  -t lscr.io/linuxserver/kometa:latest .

The ARM variants can be built on x8664 hardware and vice versa using lscr.io/linuxserver/qemu-static
docker run --rm --privileged lscr.io/linuxserver/qemu-static --reset

Once registered you can define the dockerfile to use with -f Dockerfile.aarch64.
Versions
05.07.26: - Rebase to Alpine 3.24.
28.12.25: - Rebase to Alpine 3.23.
09.07.25: - Rebase to Alpine 3.22.
06.01.25: - Rebase to Alpine 3.21.
24.06.24: - Rebase to Alpine 3.20.
22.04.24: - Initial Release.

Serve Kometa 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.

Proxy Domain App port Upstream

Proxying kometa.example.com to http://Kometa:80

Add this to your Caddyfile

kometa.example.com {
	reverse_proxy http://Kometa:80
}

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 Kometa
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:80 failed: port is already allocated", something else on your server is using that port.

Find what's using it: sudo ss -tlnp | grep :80
Stop the other service, or pick a different host port. In 80:80 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:80. The 0.0.0.0 link Portainer shows isn't a real address.
Give it a minute after first deploy, Kometa can take a while to initialise.
Make sure your firewall allows the port, e.g. sudo ufw allow 80

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 /srv/lsio/kometa/config
Or set the PUID and PGID variables (defaults 1000:1000) to match your own user, found with id $USER

Image won't pull

Test the pull directly on the host: docker pull linuxserver/kometa: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.

Container keeps restarting

The unless-stopped restart policy relaunches the app after every crash, so the real error can scroll past.

Check the logs right after a restart, the last few lines before it died are the useful ones.
Get the exit code with docker inspect Kometa --format '{{.State.ExitCode}}'
Still stuck? Redeploy once with the restart policy set to no so the failure stays visible.

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 on Kometa-Team/Kometa
Template not working: Open an issue on technorabilia/portainer-templates
This website not working: Open an issue on lissy93/portainer-templates

Similar apps

Bazarr (container) Media Management

Handbrake Media Management

Lidarr Media Management

Mediaelch Media Management

Medusa (container) Media Management

Mylar3 Media Management

Radarr Media Management

Sickgear Media Management