mirror of
https://github.com/MacRimi/ProxMenux.git
synced 2026-09-29 18:16:43 +00:00
MacRimiandClaude Opus 5.5
4437a671d2
OCI manager Apps - App tab: containers installed from an OCI image are identified from their installation record; the application and image versions are shown and an update is detected by image digest; repository link; Refresh data. - Updates tab for OCI containers: Update and Recreate run the same flow as the OCI menu in the Monitor terminal; the pre-update backup can be kept in a backup storage; scheduled image updates with an optional minimum age. - Logs tab: console output of the application, kept on the host (lxc.console.logfile + logrotate) and followed live. - The Proxmox console opens a shell (cmode: shell) when the image has one. - A damaged image download is fetched again before failing. - Multi-container applications open at their LAN address; volume mount points on block storage report their usage. Monitor - Proxmox notifications are delivered to a loopback-only HTTP listener when HTTPS is enabled, so they no longer fail certificate verification. - Log persistence counts recurring patterns only; an ended burst is not reported as persistent and its warning clears on its own (#386). - Proxmox notification config backups are deduplicated and capped at three. - The update icon on the Apps page opens the container on its Updates tab. - Version 1.2.6.2-beta and its release notes in every Monitor language. Docs - OCI manager Apps and Audit & Report rebuilt as per-page message files, with a new page for OCI containers in the Monitor. - Seven pages fixed where rich-text tags were missing from t.rich. Translations - Spanish fixes across the OCI engine, the Monitor and the TUI menus. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
409 lines
21 KiB
JSON
409 lines
21 KiB
JSON
{
|
|
"schema_version": "0.5.0",
|
|
"kind": "proxmenux.oci-template",
|
|
"id": "image-trilium",
|
|
"status": "laboratory-validated",
|
|
"catalog_ui": {
|
|
"title": {
|
|
"en_US": "Trilium"
|
|
},
|
|
"tagline": {
|
|
"en_US": "Build your personal knowledge base with TriliumNext Notes"
|
|
},
|
|
"description": {
|
|
"en_US": "TriliumNext Notes is a cross-platform hierarchical note-taking tool focused on building large personal knowledge bases, offering robust organization and editing capabilities. Its intuitive interface and versatile features make it ideal for scholars, developers, and note-taking enthusiasts managing complex knowledge.\n\nThe tool's core features include hierarchical note organization and rich editing. Users can arrange notes in an arbitrarily deep tree structure, with single notes clonable to multiple locations. It supports a WYSIWYG editor with tables, images, math, and Markdown autoformatting for efficiency. Code notes feature syntax highlighting, while fast navigation includes full-text search and note hoisting. Seamless versioning and note attributes enable organization, querying, and advanced scripting.\n\nIt offers secure login (OpenID, TOTP), supports self-hosted synchronization servers or third-party services, and provides per-note encryption for privacy. Users can sketch diagrams with Excalidraw, create relation/link maps, mind maps with Mind Elixir, and geo maps with location pins and GPX tracks. A REST API enables automation, with scalability for over 100,000 notes. Touch-optimized mobile frontend, dark theme, user themes, Evernote/Markdown import/export, and Web Clipper enhance usability.\n\n**Key Features:**\n- Notes can be arranged into arbitrarily deep tree. Single note can be placed into multiple places in the tree (see [cloning](https://triliumnext.github.io/Docs/Wiki/cloning-notes))\n- Rich WYSIWYG note editor including e.g. tables, images and [math](https://triliumnext.github.io/Docs/Wiki/text-notes) with markdown [autoformat](https://triliumnext.github.io/Docs/Wiki/text-notes#autoformat)\n- Support for editing [notes with source code](https://triliumnext.github.io/Docs/Wiki/code-notes), including syntax highlighting\n- Fast and easy [navigation between notes](https://triliumnext.github.io/Docs/Wiki/note-navigation), full text search and [note hoisting](https://triliumnext.github.io/Docs/Wiki/note-hoisting)\n- Seamless [note versioning](https://triliumnext.github.io/Docs/Wiki/note-revisions)\n- Note [attributes](https://triliumnext.github.io/Docs/Wiki/attributes) can be used for note organization, querying and advanced [scripting](https://triliumnext.github.io/Docs/Wiki/scripts)\n- Direct [OpenID and TOTP integration](https://github.com/TriliumNext/Trilium/blob/main/docs/User%20Guide/User%20Guide/Installation%20%26%20Setup/Server%20Installation/Multi-Factor%20Authentication.md) for more secure login\n- [Synchronization](https://triliumnext.github.io/Docs/Wiki/synchronization) with self-hosted sync server\n - there's a [3rd party service for hosting synchronisation server](https://trilium.cc/paid-hosting)\n- [Sharing](https://triliumnext.github.io/Docs/Wiki/sharing) (publishing) notes to public internet\n- Strong [note encryption](https://triliumnext.github.io/Docs/Wiki/protected-notes) with per-note granularity\n- Sketching diagrams, based on [Excalidraw](https://excalidraw.com/) (note type canvas)\n- [Relation maps](https://triliumnext.github.io/Docs/Wiki/relation-map) and [link maps](https://triliumnext.github.io/Docs/Wiki/link-map) for visualizing notes and their relations\n- Mind maps, based on [Mind Elixir](https://docs.mind-elixir.com/)\n- [Geo maps](https://github.com/TriliumNext/Trilium/blob/main/docs/User%20Guide/User%20Guide/Note%20Types/Geo%20Map.md) with location pins and GPX tracks\n- [Scripting](https://triliumnext.github.io/Docs/Wiki/scripts) - see [Advanced showcases](https://triliumnext.github.io/Docs/Wiki/advanced-showcases)\n- [REST API](https://triliumnext.github.io/Docs/Wiki/etapi) for automation\n- Scales well in both usability and performance upwards of 100 000 notes\n- Touch optimized [mobile frontend](https://triliumnext.github.io/Docs/Wiki/mobile-frontend) for smartphones and tablets\n- Built-in [dark theme](https://triliumnext.github.io/Docs/Wiki/themes), support for user themes\n- [Evernote](https://triliumnext.github.io/Docs/Wiki/evernote-import) and [Markdown import & export](https://triliumnext.github.io/Docs/Wiki/markdown)\n- [Web Clipper](https://triliumnext.github.io/Docs/Wiki/web-clipper) for easy saving of web content\n- Customizable UI (sidebar buttons, user-defined widgets,...)\n- [Metrics](https://github.com/TriliumNext/Trilium/blob/main/docs/User%20Guide/User%20Guide/Advanced%20Usage/Metrics.md), along with a [Grafana Dashboard](https://github.com/TriliumNext/Trilium/blob/main/docs/User%20Guide/User%20Guide/Advanced%20Usage/Metrics/grafana-dashboard.json)\n\n**Learn More:**\n- [TriliumNext GitHub Repository](https://github.com/TriliumNext/Trilium)\n- [awesome-trilium](https://github.com/Nriver/awesome-trilium) for 3rd party themes, scripts, plugins and more\n- [TriliumRocks!](https://trilium.rocks/) for tutorials, guides, and much more\n"
|
|
},
|
|
"category": "documents",
|
|
"category_label": "Documents & Notes",
|
|
"author": "zadam",
|
|
"developer": "zadam",
|
|
"icon": "https://cdn.jsdelivr.net/gh/homarr-labs/dashboard-icons@main/webp/trilium.webp",
|
|
"thumbnail": null,
|
|
"screenshots": [],
|
|
"architectures": [
|
|
"amd64",
|
|
"arm64"
|
|
],
|
|
"launch": {
|
|
"scheme": "http",
|
|
"port": 8080,
|
|
"path": "/"
|
|
},
|
|
"website": "https://triliumnext.github.io/Docs/",
|
|
"documentation": null,
|
|
"repository": "https://hub.docker.com/r/triliumnext/trilium",
|
|
"tips": [],
|
|
"mini_changelog": [],
|
|
"display_version": null,
|
|
"updated_at": null
|
|
},
|
|
"source": {
|
|
"provider": "official",
|
|
"repository": "https://hub.docker.com/r/triliumnext/trilium",
|
|
"revision": "0f07c00bf1b80f8303a5fea1f327c85c74a2d1de2b3c5ed1763c370fd21532a0",
|
|
"image_repository_url": "https://hub.docker.com/r/triliumnext/trilium",
|
|
"readme_pushed_at": "2026-09-11T10:43:22Z",
|
|
"compose_sha256": "0f07c00bf1b80f8303a5fea1f327c85c74a2d1de2b3c5ed1763c370fd21532a0",
|
|
"generated_at": "2026-09-13T15:35:03+00:00"
|
|
},
|
|
"container_contract": {
|
|
"service_name": "trilium",
|
|
"container_name": "trilium",
|
|
"image": {
|
|
"reference": "triliumnext/trilium:latest",
|
|
"registry": "docker.io",
|
|
"repository": "triliumnext/trilium",
|
|
"tag": "latest",
|
|
"digest": null,
|
|
"pull_policy": "resolve-selected-tag-to-architecture-digest-at-install"
|
|
},
|
|
"environment": [],
|
|
"volumes": [
|
|
{
|
|
"id": "volume-0",
|
|
"container_path": "/home/node/trilium-data",
|
|
"compose_source_example": "/DATA/AppData/$AppID",
|
|
"read_only": false,
|
|
"required": true,
|
|
"installation_choice": [
|
|
"managed-volume",
|
|
"host-bind"
|
|
],
|
|
"default": "managed-volume",
|
|
"managed_volume": {
|
|
"backup": true,
|
|
"default_size_gb": 8
|
|
}
|
|
}
|
|
],
|
|
"ports": [
|
|
{
|
|
"container_port": 8080,
|
|
"published_example": 8088,
|
|
"protocol": "tcp",
|
|
"required": true,
|
|
"proxmox_behavior": "listener-on-dedicated-lxc-address-no-nat"
|
|
}
|
|
],
|
|
"related_services": [],
|
|
"restart": "unless-stopped",
|
|
"stop_grace_period": null,
|
|
"original_compose": "name: trilium\nservices:\n trilium:\n command: []\n container_name: trilium\n deploy:\n resources:\n reservations:\n memory: 256M\n image: triliumnext/trilium:latest\n ports:\n - target: 8080\n published: '8088'\n protocol: tcp\n restart: unless-stopped\n volumes:\n - type: bind\n source: /DATA/AppData/$AppID\n target: /home/node/trilium-data\n network_mode: bridge\n privileged: false\n"
|
|
},
|
|
"compose_stack": {
|
|
"project_name": "trilium",
|
|
"deployment_model": "one-native-oci-lxc-per-compose-service",
|
|
"user_experience": "single-application-install",
|
|
"main_service": "trilium",
|
|
"service_count": 1,
|
|
"services": [
|
|
{
|
|
"name": "trilium",
|
|
"image": "triliumnext/trilium:latest",
|
|
"is_main": true,
|
|
"role": "frontend",
|
|
"vmid_offset": 0,
|
|
"depends_on": [],
|
|
"frontend_network": true,
|
|
"private_network": false,
|
|
"compose": {
|
|
"command": [],
|
|
"container_name": "trilium",
|
|
"deploy": {
|
|
"resources": {
|
|
"reservations": {
|
|
"memory": "256M"
|
|
}
|
|
}
|
|
},
|
|
"image": "triliumnext/trilium:latest",
|
|
"ports": [
|
|
{
|
|
"target": 8080,
|
|
"published": "8088",
|
|
"protocol": "tcp"
|
|
}
|
|
],
|
|
"restart": "unless-stopped",
|
|
"volumes": [
|
|
{
|
|
"type": "bind",
|
|
"source": "/DATA/AppData/$AppID",
|
|
"target": "/home/node/trilium-data"
|
|
}
|
|
],
|
|
"network_mode": "bridge",
|
|
"privileged": false
|
|
}
|
|
}
|
|
],
|
|
"top_level": {
|
|
"name": "trilium"
|
|
},
|
|
"networking": {
|
|
"frontend": "selected-proxmox-bridge",
|
|
"private_required": false,
|
|
"private_creation": "automatic-create-if-missing",
|
|
"private_address_allocation": "automatic-static-address-per-service",
|
|
"service_discovery": "private-addresses-with-compose-service-host-aliases",
|
|
"dependency_external_access": "disabled-unless-service-publishes-ports",
|
|
"prompt_user_for_private_network": false
|
|
},
|
|
"storage": [
|
|
{
|
|
"id": "trilium-volume-0",
|
|
"service": "trilium",
|
|
"container_path": "/home/node/trilium-data",
|
|
"mode": "managed-volume",
|
|
"user_selectable": false,
|
|
"backup": true,
|
|
"shared_with_other_lxc": false,
|
|
"source_path": null,
|
|
"source_path_prompt": null
|
|
}
|
|
],
|
|
"orchestration": {
|
|
"reserve_vmids_atomically": 1,
|
|
"start_order": [
|
|
"trilium"
|
|
],
|
|
"stop_order": [
|
|
"trilium"
|
|
],
|
|
"dependency_readiness": "compose-healthcheck-then-port-or-process-fallback",
|
|
"rollback_on_failure": "remove-new-rootfs-preserve-created-persistent-volumes"
|
|
},
|
|
"installer_inputs": {
|
|
"prompted": [
|
|
"stack_name",
|
|
"base_vmid",
|
|
"rootfs_storage",
|
|
"persistent_data_destinations",
|
|
"frontend_bridge",
|
|
"frontend_ipv4_mode"
|
|
],
|
|
"automatic": [
|
|
"dependent_vmids",
|
|
"private_bridge",
|
|
"private_subnet",
|
|
"private_service_addresses",
|
|
"compose_service_aliases",
|
|
"generated_secrets",
|
|
"dependency_start_and_stop_order"
|
|
],
|
|
"generated_secrets": []
|
|
}
|
|
},
|
|
"first_run": {
|
|
"endpoints": [
|
|
{
|
|
"label": "Web UI",
|
|
"scheme": "http",
|
|
"port": 8080,
|
|
"path": "/",
|
|
"source": "compose-metadata"
|
|
}
|
|
],
|
|
"credentials": []
|
|
},
|
|
"proxmox": {
|
|
"runtime": "native-oci-lxc",
|
|
"technology_status": "proxmox-technology-preview",
|
|
"defaults": {
|
|
"unprivileged": true,
|
|
"ostype": "auto-from-image",
|
|
"cores": 2,
|
|
"memory_mb": 256,
|
|
"swap_mb": 512,
|
|
"rootfs_size_gb": 8,
|
|
"rootfs_storage": "local-lvm",
|
|
"volume_storage": "local-lvm",
|
|
"template_storage": "local",
|
|
"bridge": "vmbr0",
|
|
"ipv4": "dhcp",
|
|
"firewall": true,
|
|
"host_managed_network": true,
|
|
"onboot": false,
|
|
"features": [
|
|
"nesting=1"
|
|
],
|
|
"shutdown_timeout_seconds": 30
|
|
},
|
|
"image_metadata_policy": {
|
|
"entrypoint": "import-from-oci-image",
|
|
"cmd": "import-from-oci-image",
|
|
"environment": "import-image-env-then-apply-compose-overrides",
|
|
"user": "import-from-oci-image",
|
|
"working_dir": "import-from-oci-image",
|
|
"stop_signal": "import-from-oci-image"
|
|
},
|
|
"installer_profile": {
|
|
"runtime": {
|
|
"command": []
|
|
}
|
|
},
|
|
"adaptations": [
|
|
{
|
|
"id": "imported-compose-source",
|
|
"upstream_behavior": "The source definition deploys the complete Docker Compose application model.",
|
|
"native_lxc_behavior": "The source model is preserved and remains blocked until every service option has a reviewed native Proxmox mapping.",
|
|
"reason": "Catalog import must not imply runtime compatibility.",
|
|
"behavioral_impact": "No automatic installation before review.",
|
|
"validation": "pending-per-application"
|
|
},
|
|
{
|
|
"id": "rolling-latest-image",
|
|
"upstream_behavior": "A discovered Compose may pin a release tag or digest.",
|
|
"native_lxc_behavior": "ProxMenux selects the same image repository with the latest tag for catalog installations.",
|
|
"reason": "The automatic catalog intentionally offers rolling latest images; pinned versions belong to the future manual installer.",
|
|
"behavioral_impact": "The installed release can be newer than the discovered Compose revision.",
|
|
"validation": "pending-per-application"
|
|
},
|
|
{
|
|
"id": "dedicated-lxc-network",
|
|
"upstream_behavior": "Docker publishes selected container ports on the Docker host.",
|
|
"native_lxc_behavior": "A reviewed native application will listen on its original container ports at a dedicated LXC address.",
|
|
"reason": "A native LXC has its own address and does not require Docker port NAT.",
|
|
"behavioral_impact": "Published ports are metadata; ProxMenux URLs use the matching container target port.",
|
|
"validation": "pending-per-application"
|
|
},
|
|
{
|
|
"id": "compose-shm-size",
|
|
"upstream_behavior": "Compose sets the size of the container /dev/shm tmpfs.",
|
|
"native_lxc_behavior": "ProxMenux mounts a native LXC tmpfs at /dev/shm with the same requested capacity.",
|
|
"reason": "The OCI image runs directly as an LXC and therefore needs the equivalent Proxmox mount entry.",
|
|
"behavioral_impact": "None expected.",
|
|
"validation": "not-requested-by-compose"
|
|
},
|
|
{
|
|
"id": "compose-command",
|
|
"upstream_behavior": "Compose replaces the image Cmd while retaining its Entrypoint.",
|
|
"native_lxc_behavior": "ProxMenux reads the official OCI Entrypoint and combines it with the Compose command as the native LXC init command.",
|
|
"reason": "Proxmox stores the effective OCI process as one entrypoint string.",
|
|
"behavioral_impact": "None expected.",
|
|
"validation": "pending-per-application"
|
|
},
|
|
{
|
|
"id": "compose-privileged-mode",
|
|
"upstream_behavior": "Compose selects whether the container runs in privileged mode.",
|
|
"native_lxc_behavior": "ProxMenux uses a privileged LXC only after an explicit high-risk confirmation; otherwise it keeps the LXC unprivileged.",
|
|
"reason": "The native OCI-LXC deployment must preserve the requested privilege level without silently weakening isolation.",
|
|
"behavioral_impact": "A privileged LXC has weaker isolation from the Proxmox host.",
|
|
"validation": "native-equivalent"
|
|
},
|
|
{
|
|
"id": "compose-process-runtime",
|
|
"upstream_behavior": "Compose can replace Entrypoint, User and WorkingDir and request an init process or interactive terminal.",
|
|
"native_lxc_behavior": "ProxMenux applies the process overrides through native LXC init directives; lxc-init provides PID 1 supervision and the CT console provides terminal access.",
|
|
"reason": "The OCI process must start with the same identity, command and working directory without Docker.",
|
|
"behavioral_impact": "Compose stdin_open and tty become access through the Proxmox LXC console.",
|
|
"validation": "not-requested-by-compose"
|
|
},
|
|
{
|
|
"id": "compose-healthcheck",
|
|
"upstream_behavior": "Docker periodically executes the declared container healthcheck.",
|
|
"native_lxc_behavior": "For a single-service LXC, ProxMenux translates HTTP localhost checks into a mandatory first-start service check.",
|
|
"reason": "Proxmox has no persistent Docker health state, while the installer still must detect a failed first boot.",
|
|
"behavioral_impact": "The check runs during installation rather than continuously after installation.",
|
|
"validation": "not-requested-by-compose"
|
|
},
|
|
{
|
|
"id": "compose-cpu-priority",
|
|
"upstream_behavior": "Docker cpu_shares sets a relative scheduling weight with 1024 as its neutral value.",
|
|
"native_lxc_behavior": "ProxMenux converts the relative weight to Proxmox cpuunits with 100 as its neutral value and lets the user review it.",
|
|
"reason": "Both settings express relative CPU priority on different scales.",
|
|
"behavioral_impact": "Rounding and Proxmox minimum limits can slightly change very low weights.",
|
|
"validation": "not-requested-by-compose"
|
|
},
|
|
{
|
|
"id": "compose-network-identity",
|
|
"upstream_behavior": "Compose can set hostname, MAC address, extra hosts and attach a service to Docker networks.",
|
|
"native_lxc_behavior": "ProxMenux applies hostname and MAC to net0, writes additional host aliases into the LXC and uses its dedicated bridge connection for single-service networks.",
|
|
"reason": "A dedicated LXC has its own network namespace and does not need a Docker bridge per service.",
|
|
"behavioral_impact": "host-gateway resolves to the IPv4 address of the selected Proxmox bridge.",
|
|
"validation": "not-requested-by-compose"
|
|
},
|
|
{
|
|
"id": "docker-engine-metadata",
|
|
"upstream_behavior": "Compose labels annotate Docker objects and the json-file logging driver rotates Docker-managed logs.",
|
|
"native_lxc_behavior": "Labels remain source metadata; Docker json-file settings are not applied because the OCI process runs directly under LXC.",
|
|
"reason": "There is no Docker object or Docker json-file log behind a native OCI-LXC application.",
|
|
"behavioral_impact": "Docker-only label consumers and Docker log-driver rotation do not exist in the native deployment.",
|
|
"validation": "pending-per-application"
|
|
},
|
|
{
|
|
"id": "compose-device-passthrough",
|
|
"upstream_behavior": "Compose passes host character devices or requests an NVIDIA runtime GPU.",
|
|
"native_lxc_behavior": "ProxMenux converts recognized device declarations to native Proxmox dev resources; NVIDIA profiles also inject compatible host driver libraries read-only.",
|
|
"reason": "Native OCI-LXC does not execute Docker device or NVIDIA runtime hooks.",
|
|
"behavioral_impact": "Hardware is exposed only after explicit user confirmation and host-path validation.",
|
|
"validation": "not-requested-by-compose"
|
|
},
|
|
{
|
|
"id": "compose-host-ipc",
|
|
"upstream_behavior": "ipc: host shares the Docker host IPC namespace, commonly to avoid Docker's small default shared-memory allocation.",
|
|
"native_lxc_behavior": "The application keeps the LXC IPC namespace and receives a configurable 1 GiB /dev/shm instead of sharing Proxmox host IPC.",
|
|
"reason": "Processes in a single native LXC already share one IPC namespace; retaining isolation is safer than exposing host IPC.",
|
|
"behavioral_impact": "The application cannot exchange IPC objects with processes on the Proxmox host.",
|
|
"validation": "not-requested-by-compose"
|
|
}
|
|
]
|
|
},
|
|
"compatibility": {
|
|
"automatic_install_candidate": true,
|
|
"validated": false,
|
|
"supported_compose_keys": [
|
|
"command",
|
|
"container_name",
|
|
"cpu_shares",
|
|
"deploy",
|
|
"devices",
|
|
"entrypoint",
|
|
"environment",
|
|
"extra_hosts",
|
|
"healthcheck",
|
|
"hostname",
|
|
"image",
|
|
"init",
|
|
"ipc",
|
|
"labels",
|
|
"logging",
|
|
"mac_address",
|
|
"network_mode",
|
|
"networks",
|
|
"ports",
|
|
"privileged",
|
|
"restart",
|
|
"runtime",
|
|
"shm_size",
|
|
"stdin_open",
|
|
"stop_grace_period",
|
|
"tty",
|
|
"user",
|
|
"volumes",
|
|
"working_dir"
|
|
],
|
|
"untranslated_blockers": [],
|
|
"policy": "Single-image definitions are installable when every declared Compose option has a native Proxmox translation. Multi-image and unsupported runtime features remain blocked until their orchestrator or mapping is available."
|
|
},
|
|
"validation": {
|
|
"schema": "passed-at-generation",
|
|
"clean_install": "passed-amd64",
|
|
"service_health": "passed-amd64",
|
|
"restart_persistence": "pending",
|
|
"backup_restore": "pending",
|
|
"update_preserves_data": "pending"
|
|
},
|
|
"lifecycle": {
|
|
"update_strategy": "resolve-latest-image-then-apply-reviewed-native-lxc-update",
|
|
"registry_state": {
|
|
"resolved_architecture": null,
|
|
"resolved_digest": null,
|
|
"image_version_label": null,
|
|
"image_created": null
|
|
},
|
|
"change_detection": "compare-compose-sha256-and-resolved-latest-image-digest",
|
|
"automatic_unattended_updates": false
|
|
}
|
|
}
|