Last changes before version 1.2.7.
OCI manager Apps
- Multi-container applications start while one of their containers is
being backed up: the start hook waits until vzdump releases it and does
not start it twice. The DHCP client of a dependency no longer keeps the
lock of the hook, so later starts do not hang, and the watchdog waits
while a dependency is locked. Installing or updating ProxMenux replaces
the published copies of the hook already in place.
- Images built from scratch with a numeric user, such as ddns-updater,
install: the container is created from a copy of the image that adds
the /etc/passwd and /etc/group Proxmox VE needs, and the application
runs with the user the image declares. The downloaded image stays
unchanged. An image with a named user and no user database stops
before anything is created, with a message that says why.
Catalog
- Twelve new applications: MDBListarr, CrossWatch, Free Games Claimer
Remaster, Cloudreve, Poznote and AceStream HTTP Proxy, suggested in
discussion #440, and the Dockur images of Chrony, Dnsmasq, Tor,
Stunnel, strfry and Statping. The catalog lists 347 applications.
- Their prompts, labels and notes are translated into the seven
languages of the menus.
Documentation
- OCI manager: architecture, lifecycle and stacks pages revised, with
larger diagrams and new screenshots.
- Contributors: the page now thanks those developing, reviewing,
translating and testing ProxMenux today and those who helped in its
first steps, with new avatars.
Tests for the stack start hook, the watchdog, the user database check
of OCI images and the Tor installation summary.
The installation record of an OCI application travels with its container:
a copy inside the container and another in /etc/pve, written together
with the one kept on the host. A container restored on a newly installed
Proxmox, restored with another ID or moved to another node of a cluster
is recognised and registered again, with its private network, hookscript,
Rclone mount, host firewall rule and NVIDIA runtime. The Monitor offers
the same recovery from the Updates tab.
AMD GPUs are offered by generation. A GPU the ROCm image supports takes
the profile as it is; one of a supported family (Radeon 680M, 780M) is an
experimental option that asks for confirmation and is never proposed; an
older one is not offered. The GPU is checked with a real inference before
the installation accepts it. Recreate changes what runs recognition in an
installed Immich, between the CPU and a GPU of the host.
Updates:
- A failed update that is restored and checked removes its temporary
container and the disks of the failed attempt.
- Every container volume is part of the backups, so Jellyfin, Plex and
Hugo update with their default installation.
- An image published with a Docker-format manifest is recognised by its
layers and build time and updates.
- The Proxmox notes of a multi-container application link to its LAN
address.
Adds the OCI manager: an engine that turns a Docker Compose file into an
LXC definition, a catalog of 365 applications drawn from LinuxServer.io
and other container image sources, and a per-instance registry recording
what each container was built from. Reachable from the main menu.
Catalog text is translated like every other string in the project: the
taglines go through translate() and land in lang/*.json, so the entries
read in all eight languages instead of only English.
Translation cache builder:
- a failed translation leaves the key absent rather than writing English,
which previously made the string count as translated forever
- a result identical to a 3+ word source is rejected, catching a provider
that silently returns the text it was given
- strings that are nothing but glossary terms keep their source spelling
instead of being discarded as failures
- no backoff between attempts when the provider is deterministic
- application names are protected so "HAOS One" survives translation
- argos joins the provider list, and the workflow reads the OCI sources
Audit & Report:
- findings that moved in the wrong direction between runs are reported
alongside the ones that improved
- an accepted risk can carry a review date and is flagged when it falls due
- backup checks explain in plain language what they looked at and what to
do next
Monitor:
- disks can be excluded from periodic reads, and an idle disk says so
instead of showing a stale temperature
- per-disk identity survives a controller or enclosure change
- scheduled Borg backups resolve their SSH key from the repository entry
- PVE upgrades log the package list and the resulting dpkg changes
The web build no longer copies scripts/ into public/: the documentation
links to GitHub, so nothing read that folder.
Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>
MacRimi
