Skip to content
TrueForge

News

TrueTech

GamingForge

LifeForge

TrueCharts News

Announcing: ContainerForge

Kjeld Schouten
Kjeld Schouten
Ops and R&D Lead

We’re excited to finally introduce ContainerForge, a new project under the TrueForge–TrueTech umbrella — and the foundation for all future TrueCharts containers!

🔗 Learn more: trueforge.org/truetech/containerforge
💬 Join the discussion: on our Discord
💻 Explore the code: github.com/trueforge-org/containerforge 💖 Support our work: Sponsor us on GitHub or OpenCollective

🧩 What Is ContainerForge?

Section titled “🧩 What Is ContainerForge?”

ContainerForge is an opinionated collection of container images — focused on being efficient, consistent, and easy to maintain.

Our containers follow modern standards and proven best practices:

  • ✅ Rootless by default (568:568) for security and compatibility
  • ✅ Multi-architecture builds (x86 and ARM)
  • ✅ Semantically versioned and digest-pinnable for predictable updates
  • ✅ Single-process design for simplicity and transparency

Our guiding principle is simple:

“Build efficient, standardised and secure containers.”

⚙️ Built with TrueNAS in Mind

Section titled “⚙️ Built with TrueNAS in Mind”

While ContainerForge isn’t built exclusively for TrueNAS, it’s designed to work exceptionally well with TrueNAS’ Custom App and Docker Compose deployment options.

Here’s how we make that experience smoother:

  • Correct Default User (568:568) – Matches TrueNAS’ Apps user to avoid permission issues
  • Automatic Update Control – TrueNAS can automatically track and update containers by digest, patch, minor, or major version
  • Consistent Configuration Paths – Standardized /config directories simplify backups and migration
  • Ubuntu-based Base Images – Ensuring stable, secure, and well-supported foundations

These considerations make deploying ContainerForge images on TrueNAS a clean and predictable experience — without needing extra tweaks or compatibility layers.

🧱 Standardised, Extensible, and Transparent

Section titled “🧱 Standardised, Extensible, and Transparent”

ContainerForge builds upon the experience of existing projects such as home-operations, linuxserver.io, and hotio.dev.

What makes it different:

  • Consistent Standards — All images follow a unified base and structure
  • Transparency — Each build is verifiable with GitHub Actions attestations
  • Community Alignment — Designed for TrueCharts integration and home-lab friendliness

And because every image shares a common, well-defined base (Ubuntu, Python, Node, Golang, Java, etc.), ContainerForge enables fast, reliable updates across the board.

🧰 What’s Next

Section titled “🧰 What’s Next”

This is only the beginning.
We’re planning to expand ContainerForge with pre-made example Docker Compose files, making deployment even easier for users who prefer direct container setups over Helm or Kubernetes.

Our long-term goal: provide a complete, consistent container ecosystem that works great everywhere — whether through TrueCharts, TrueNAS, or standalone Docker Compose setups.

📦 Explore Today

Section titled “📦 Explore Today”

Start exploring the collection now:
👉 GitHub Packages

Full documentation and details:
👉 trueforge.org/truetech/containerforge

💬 Get Involved

Section titled “💬 Get Involved”

ContainerForge is an open, community-driven project.
We welcome feedback, contributions, and discussions from everyone interested in building and running better containers.

Join us on GitHub or Discord, and help shape the next generation of container infrastructure for the TrueForge ecosystem.

Updated OCI Repository Link

Alfred Göppel
Alfred Göppel
Community Development Lead

Move OCI Registry to New Domain and Responds to Bitnami Changes

Section titled “Move OCI Registry to New Domain and Responds to Bitnami Changes”

The OCI repository has been moved from tccr.io to oci.trueforge.org

New Registry Locations

Section titled “New Registry Locations”

All images and charts previously hosted on tccr.io are now available under the new domain:

  • Images: oci.trueforge.org/tccr/IMAGE
  • Charts: helm install mychart oci://oci.trueforge.org/truecharts/CHART

This change affects only the domain; the registry remains OCI-based as before. Users are encouraged to update their Helm configurations and image references accordingly to avoid interruptions.

Clustertool Updated for Talos 1.11.0

Section titled “Clustertool Updated for Talos 1.11.0”

We’re excited to share that we now support Talos 1.11 and Kubernetes 1.34! With the recent update to clustertool, managing and deploying clusters on these versions has never been easier. This ensures smoother operations, up-to-date features, and a more reliable experience for all our users.

Bitnami Policy Shift

Section titled “Bitnami Policy Shift”

Alongside the domain migration, We want to highlight the recent upstream changes from Bitnami. The popular container provider has moved to a “latest-only” publishing model for free users, meaning older tags will no longer be maintained and soon to be removed.

In addition, Bitnami has removed some images entirely, forcing the deprecation of affected TrueCharts applications such as:

  • Solr
  • Matomo

Nextcloud Update 31.0.8

Section titled “Nextcloud Update 31.0.8”

addition, we’ve fixed Nextcloud image creation and released version 31.0.8 for our charts. This update ensures smoother deployments and improved reliability, so you can run Nextcloud with confidence on your clusters.

What Users Should Do:

Section titled “What Users Should Do:”

Update all references from tccr.io to oci.trueforge.org and update their charts and clustertool to the latest version.

Expect Bitnami-based charts to stay stable thanks to digest pinning.

Note that applications relying on deprecated Bitnami images are no longer available via TrueCharts.

We emphasize our commitment to stability and transparency, while continuing to adapt to upstream changes.

Common-2025 finally released

Alfred Göppel
Alfred Göppel
Community Development Lead

TrueCharts Releases common-2025 Helm Library with Major Improvements

Section titled “TrueCharts Releases common-2025 Helm Library with Major Improvements”

The TrueCharts team is proud to announce the release of common-2025, the latest version of the shared Helm chart library powering all TrueCharts charts. This major update delivers powerful new features, improved integrations, and essential structural upgrades that enhance usability, maintainability, and compatibility across the board.

🚀 Key Highlights of common-2025

Section titled “🚀 Key Highlights of common-2025”

  • 🔐 Nginx Ingress Integration

    • Disabled by default for a cleaner baseline
    • Built-in support for:
      • Authentication
      • IP whitelisting
      • ThemePark styling

  • 🛠 GitOps CNPG Recovery Enhancements

    • No more need to bump revision numbers during CNPG cluster recovery
    • Using the revision number is now optional.

  • 🌐 Traefik Updates

    • Disabled by default for a cleaner baseline
    • Complete rework of Traefik middlewares, now defined per chart

  • 📦 Resource Management

    • Updated defaults for required pod resources

  • 🔑 Existing Pull Secret Support

    • Added support for using existing Kubernetes secrets for container registry authentication
    • Simplifies integration in environments with pre-configured imagePullSecrets

  • 🧩 Addon System Rework

    • Safe upgrade: prevents updates when some legacy addon layouts are present
    • More configuration options for addons, including:
      • Full access to the workload definition

  • 📁 Structural Cleanups

    • Removal of deprecated Portal (legacy from SCALE)
    • Major improvements to notes.txt
    • Moved MetalLB and Traefik service annotations to centralized integration logic

  • 📊 Autoscaling Enhancements

    • Refactored Horizontal Pod Autoscaler (HPA): To comply to our coding standards and testing regime
    • Added support for Vertical Pod Autoscaler (VPA): Allows for automatically adjusts CPU and memory limits over time

  • 👤 Service Account Overrides

    • Added support to optionally override the service account name in the workload podSpec

  • 🌐 Topology Key Configuration

    • Users can now configure a default topologyKey for scheduling behavior

  • 📌 Pod Affinity Support

    • Added full support for pod affinity, enabling more advanced workload placement strategies
    • Default pod affinity to ensure pods sharing RWO PVCs are started on the same node

🙏 Thank You

Section titled “🙏 Thank You”

This release marks another milestone in the growth of the TrueCharts ecosystem. A huge thank you to all contributors who help build, improve, and maintain all of our charts. Your work makes TrueCharts possible.

And of course, thank you to all users—your feedback, deployments, and support are what drive this project forward every day.

For more information or to get involved, visit: https://trueforge.org

Truenas-Oriented Talos Docker-Compose

Alfred Göppel
Alfred Göppel
Community Development Lead
 Kjeld Schouten
Kjeld Schouten
Ops and R&D Lead

With the release of TrueNAS SCALE Fangtooth, iXsystems has officially switched its virtualization backend from KVM to Incus. This transition has introduced several limitations, and VM support is now also labeled as experimental, leaving users without a stable VM solution on TrueNAS.

Users have reported performance issues with the new Incus-based VM system, and some previously supported configurations such as running VMs with raw-file backed disks (making use of ZFS small-blocks special-vdevs) are no longer functional. Currently, there is no official Incus-Guest-Agent available on Talos, making it difficult for users to control the VM through the TrueNAS UI.

Users have been requesting a Kubernetes solution within the iX-supported Apps/Instances system for quite some time. Traditional containerization approaches like LXC/LXD or jails were never viable options for us as they lack support for Talos and present significant management challenges. However, after careful testing and evaluation, we’ve concluded that integrating Talos in container form within the existing Docker Compose-based Apps system presents a compelling solution. This approach enables users to run Kubernetes on TrueNAS SCALE without the added complexity of virtual machines or the maintenance burden of homegrown setups, striking a practical balance between performance, simplicity and native integration.

In light of this, we have reaffirmed our commitment to the TrueNAS community by releasing a new guide on how to run Talos as a Docker container inside SCALE Apps. This approach provides a practical alternative for those affected by the VM backend changes, allowing continued experimentation and development with Talos despite the Incus limitations.

To get started with Talos as a Docker-Compose App following the following this.

MrPuffins new role

Kjeld Schouten
Kjeld Schouten
Ops and R&D Lead

Hey everyone,

Kjeld here — most of you know me as MrPuffin, or back in the day, Ornias.

Over the past year, we’ve been quietly but steadily working on something big at TrueCharts. Behind the scenes, we’ve focused hard on professionalizing and restructuring the project to make it more sustainable, more scalable, and frankly, more awesome.

Our core energy has been steadily shifting toward building out and refining our Common Chart, improving our CI/CD pipelines, and developing tooling like clustertool — all with the goal of supporting better automation and long-term maintainability. It’s been a gradual but deliberate transition in focus, setting the stage for a more sustainable future for the project.

In the meantime, the charts catalog itself has organically evolved. It’s now primarily driven by community contributions, which is incredible to see. People like Alfi and jagrbombs from our core team are doing fantastic work reviewing and maintaining the quality of incoming PRs. And let’s not forget Stavros, who’s been laser-focused on the Common Chart and pushing forward with unit tests and technical improvements.

But with all this growth comes a shift.

As life changes on my end too, I’ve come to realize I simply can’t do it all — not if we want to keep doing things right. So it’s time for a new phase.

You’ll notice on the team page that I’m officially stepping back from day-to-day involvement with the general chart catalog. That means fewer interactions from me on community chart PRs and general contributions.

Instead, I’ll be focusing 100% of my energy on what matters most for the long-term success of the project:

  • Developing new features for the Common Chart
  • Maintaining and improving our CI/CD and deployment/testing pipelines
  • Coordinating and supporting our amazing volunteer staff

In practice, that means the chart catalog will be almost entirely community-driven — and that’s by design. We’ve built the structure for it, and now it’s time to let it grow.

So, yes, you’ll probably see less of me in Discord and around the edges of the project. But rest assured, I’m still here, still fully committed, just with a more focused role behind the scenes (and on GitHub, of course).

Thanks to everyone who’s helped us get here. This isn’t the end of anything — it’s just the next logical step forward.

Onwards and upwards, Kjeld (MrPuffin)