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.
- Check that the Monitor answers on its socket, not only that it exists
- Report the applications whose check failed instead of failing the whole request
- Show those applications as not checked, without their older result
- Tell the user in the menu when a check fails
- Accept tag changes in the native stack check before recreate or update
- Keep identity and every other setting checked as before
- Add a regression test for the native stack check
- Registry accounts are kept in /etc/pve/priv/proxmenux/registry-auth.json, shared by every node, unless REGISTRY_AUTH_FILE says otherwise
- The custom image importer offers to sign in when a registry refuses an image, and reads it again
- Installers, updates, the watchdog and the Monitor update check read private images with the saved accounts
- The host backup includes the accounts, and uninstalling ProxMenux removes them and keeps the OCI records of the cluster
- Spanish written by hand and spacing fixed for the registry account messages in every locale
- Docs: private registries section, Registry accounts in the OCI menu, README storage notes
A container volume is filled with what the image holds at that path, with its owner and permissions, as Docker does with a new volume. It was only done for the recipes that asked for it. Images that run as a user of their own and do not take PUID, such as Node-RED or Grafana, find their data directory writable and start.
Jonatan
MacRimi
MacRimiandGitHub
Jonatan Castro
VAIO73