- Jelina overview
- JelinaOS
- Application management
Application management
In JelinaOS, all applications, both containerized and native, are managed through Releases: define applications in a release, deploy it to devices, and let the device agent download, install, and supervise them. Close integration with the cloud turns application management from device-by-device operations into one release applied across a fleet.
Two application models
Section titled “Two application models”| Aspect | Containerized applications | Native applications (ProgramSets) |
|---|---|---|
| Delivery format | Container image | Program package / script / binary |
| Execution environment | Container runtime | System service |
| Use cases | Modern applications, multiple services, rapid iteration | Traditional programs, deep hardware customization, real-time control |
Both models receive equal treatment within the release system: they are defined in the same release, use the same deployment workflow, and receive consistent supervision and updates.
Application lifecycle based on Releases
Section titled “Application lifecycle based on Releases”Create a Release (define container applications / native programs) │ ▼Deploy to fleet / device │ ▼Device agent synchronizes target state ──▶ Pull and install ──▶ Run and supervise │ │ │ ▼ └──────────────── Version update / rollback ◀──────── Automatic recovery| Stage | Description |
|---|---|
| Definition | Declare container images or native programs in a release, with environment, ports, dependencies, and restart policies |
| Deployment | Deploy the release to target fleets or devices; the agent applies it automatically |
| Operation | The agent supervises applications with automatic restart on failure and startup at boot |
| Update | Publish and deploy a new version for automatic device upgrades; roll back if problems occur |
Cloud releases (recommended)
Section titled “Cloud releases (recommended)”After connecting to JelinaCloud, create and deploy releases in the cloud:
- Containerized applications: specify images and runtime configuration.
- Native applications: declare program configuration (ProgramSet).
- Incremental adjustments, version switching, and rollback are supported.
See cloud application deployment and OTA.
Local management
Section titled “Local management”Without cloud connectivity, deliver target configuration through the local device management interface for the device agent to deploy. Local mode uses the same declarative configuration followed by agent execution model; applications do not depend on manual commands to keep running.
Inspect applications on the device
Section titled “Inspect applications on the device”After deployment, use device commands to inspect application status. Docker commands are for inspection and diagnostics only, not a deployment entry point:
docker ps # View container application statussystemctl list-units 'jelinvisored_*' # View native program servicesWhere to start
Section titled “Where to start”- Deploy your first application — Complete your first deployment through a release
- Cloud application deployment and OTA — Complete release and update workflow
- Native applications and ProgramSets — Release configuration for native applications