Mirrors/ProxMenux
1
0
Fork 0
mirror of https://github.com/MacRimi/ProxMenux.git synced 2026-11-02 10:52:22 +00:00
Code Issues Packages Projects Releases Wiki Activity

Apply OCI runtime settings to existing containers with recoverable edits

Browse Source
This commit is contained in:
Jonatan
2026-10-17 17:11:27 +02:00
parent d286b650d7
commit b70e968f73
15 changed files with 802 additions and 9 deletions
Download Patch File Download Diff File Expand all files Collapse all files
oci/README.md
+16 -1
View File
@@ -142,7 +142,7 @@ An application made of several images is one entry of the catalog and one instal
| Operation | What changes | What is kept |
|---|---|---|
| **Update** | The rootfs is replaced by the image the saved tag publishes today | Record, container disks, host directories, network and devices |
| **Modify** | An editor opens with the current resources, network, paths and GPU; the container is rebuilt with the changes | The data of container disks and host directories |
| **Modify** | Choose a setting, review it, then apply native LXC changes to the existing container; runtime settings may require a restart | Installed image, rootfs, persistent data and unrelated Proxmox settings |
| **Recreate** (multi-container) | Every container is rebuilt from the image it was installed with | Data, network and devices |
| **Watchdog** | Whether the application is started again when it stops on its own | Everything; only the choice is saved |
| **Remove** | The LXC, or every container of the application, its disks and its record | Host directories, with their content |
@@ -159,6 +159,21 @@ Settings changed in Proxmox VE after the installation, such as memory, cores or
A rolling tag is not an unattended update: the digest changes only through an explicit update.
For standalone applications, CPU and RAM changes apply live. Network settings,
environment overrides, directory mounts, additional managed volumes and supported
native devices use a controlled stop/start when needed. Modify does not query the
registry or download an image for these edits, even if the cached archive has
already been cleaned. Removing a managed mount detaches its disk without deleting
its data. An optional retained backup does not force recreation.
The native path checks the saved configuration and installation identity, keeps a
private before/after journal, and restores the original settings if applying them
or checking the restarted service fails. It refuses to overwrite concurrent edits.
Application-specific installer adaptations (such as changing an NVIDIA runtime or
post-start configuration) are not silently converted into a full recreation:
unsupported same-image changes stop with an explanation before modifying the CT.
Image changes and coordinated stack operations retain their separate update flow.
## From a Compose file or a docker run command to an oci-compose
The converter reads a Compose file with one service. A `docker run` command and an image reference alone are first written as a Compose file and follow the same path, so the three produce the same kind of oci-compose.