# Tugtainer

Tugtainer is a self-hosted app for automating Docker container updates. It is open source and self-hosted, installable on Docker Hub, ZimaOS and Unraid.

Canonical page: https://ourlocalhost.com/app/797/tugtainer

## Description

Tugtainer is a self-hosted app for automating Docker container updates. It offers a web user interface, providing more control than similar tools.

## Platform availability

Available on 2 of 9 platforms: Unraid, ZimaOS.

## Health score

15/100 (Low), based on 2 of 4 factors.
- Maintained: 0 (GitHub repository no longer exists)
- Easy to install: 45 (2 install platforms, install notes, Docker image)

## Links

- Docker Hub: https://hub.docker.com/r/quenary/tugtainer
- ZimaOS: https://github.com/bigbeartechworld/big-bear-casaos/tree/master/Apps/tugtainer
- Unraid: https://ca.unraid.net/apps/tugtainer-1emlftn031eadb?q=Tugtainer

## Common questions

### How do I set up agent authentication for Tugtainer?

Copy .env.example to .env and fill in values such as AGENT_SECRET, the shared secret used to verify agent connections. Skipping this can cause startup problems or leave agents less secure.

### Should I enable shell command execution for Tugtainer agents?

Keep ALLOW_EXEC=false unless you specifically need agents to run shell commands inside containers. If it is enabled, arbitrary commands may be asked to run on the host, which can break or expose your system.

### How can I expose public status endpoints?

Set ENABLE_PUBLIC_API=true only if you want public status endpoints. Leaving it off keeps extra information from being publicly available.

### Can I run Tugtainer in production?

Tugtainer is distributed as-is and is not recommended for use in a production environment.

### How do I fix a 424 or 500 agent error?

Make sure both Tugtainer and the Tugtainer agent are on the newest version. Updating the agent solved the reported 424 or 500 agent error.

---
Source: Our Local Host (https://ourlocalhost.com/app/797/tugtainer), the self-hosted and open-source app directory.