← Directory

Tugtainer

Automate updates of your Docker containers

  • Other
  • Productivity
  • Tools & Utilities
Automate updates of your Docker containers

Platform availability

Available on 2 of 9 platforms

  • Unraid
  • TrueNAS (not listed)
  • Umbrel (not listed)
  • ZimaOS
  • Proxmox (not listed)
  • Helm (not listed)
  • Mac (not listed)
  • Windows (not listed)
  • Linux (not listed)

Health score?A 0-100 score computed nightly from four factors: maintained (40%: recent commits and steady activity), popular (25%: GitHub stars, log scale), easy to install (20%: platforms, install notes, setup guides, Docker image) and light to run (15%: minimum RAM, ARM support). When the source code has been checked, a fifth factor, security check (20%: automated scan for committed secrets, unsafe desktop-app settings, known-vulnerable dependencies and project hygiene; any serious finding caps it at 20), is added. Factors without data are left out and the rest are rescaled.

15/100 Low

Maintained
0GitHub repository no longer exists
Popular
No data
Easy to install
452 install platforms, install notes, Docker image
Light to run
No data

Based on 2 of 4 factors.

Availability: platform listings confirmed today, links checked 13 days ago

No GitHub repository data collected yet.

Checked 14 days ago - source: GitHub (BigBearTechWorld/tugtainer)

Resources & Compatibility

ARM (e.g. Raspberry Pi) is supported.

Checked 14 days ago - source: Docker Hub image tags and published docs

First-install notes

  • Create and fill your .env file Copy .env.example to .env (the settings file) and fill in values like AGENT_SECRET, the shared secret used to verify agent connections. If you skip this, Tugtainer may use missing or default settings, which can cause startup problems or leave the agent less secure than intended. source
  • Leave ALLOW_EXEC off Keep ALLOW_EXEC=false unless you specifically need the agent to run shell commands (terminal commands) inside containers. If it is on, something can be asked to run arbitrary commands on the host, which can break or expose your system. source
  • Turn on public API only if needed Set ENABLE_PUBLIC_API=true only if you want public status endpoints such as /api/public/summary and /api/public/is_update_available. Leaving it off keeps extra information from being publicly available. source

Fetched 14 days ago - each note links to its source

Alternatives

No alternatives collected yet.

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.

Answers sourced from github.com, github.com, github.com, github.com

Community

Collected 13 days ago - public community threads