Using Clea OS
Overview
This section provides practical instructions for interacting with devices running Clea OS once the system is booted and operational.
Clea OS is a Yocto-based embedded Linux distribution designed for SECO hardware platforms and compatible targets.
It combines the flexibility of a standard Linux environment with the robustness and consistency required in industrial and IoT applications.
At runtime, Clea OS behaves like a complete embedded Linux system, offering both familiar user-space tools and dedicated components that extend its capabilities.
What You’ll Find in This Section
The guides in this section describe the most common runtime activities for devices running Clea OS.
They are intended for developers, system integrators, and operators who need to manage or monitor devices already flashed and booted with Clea OS.
Topics will include:
- Accessing the system through serial console, SSH, or local terminals.
- Managing network connectivity, including wired and wireless configurations.
- Using Docker for application deployment and management.
- Monitoring system health and logs for diagnostics and troubleshooting.
- Managing persistent storage and mounted volumes.
- Collecting diagnostics and checking hardware resources.
Each guide provides a mix of step-by-step procedures and reference information, allowing you to both learn and reuse commands effectively.
Typical Usage Scenarios
Devices running Clea OS are typically used in embedded and industrial contexts, such as gateways, controllers, or edge nodes.
Once powered on and connected, users can interact with the system in multiple ways depending on their role:
- Developers connect through SSH or serial interfaces to deploy applications, test configurations, and analyze logs.
- System integrators use Docker containers to install, configure, or update software components.
- Operators and technicians perform system checks, collect logs, or execute basic maintenance tasks in the field.
The goal of this section is to make these activities predictable, repeatable, and easy to perform across hardware platforms.
About the Runtime Environment
At runtime, Clea OS provides a standard Linux shell environment with all essential tools for development and maintenance.
The base image typically includes the following key components:
- Docker Engine for running and managing containerized workloads.
- Network Manager or connman for network configuration and connectivity management.
- Clea Agent for remote management and secure device communication.
- System logging and monitoring utilities for diagnostics and support.
These components are pre-integrated to work out of the box while still allowing developers to customize and extend them as needed.
Conventions Used in the Usage Guides
The following typographic conventions are used consistently throughout Clea OS documentation.
Command Contexts
| Symbol | Context | Example |
|---|---|---|
$ | Command executed on the host PC | $ git clone https://github.com/... |
$$ | Command executed inside a container on the host | $$ bitbake clea-image |
# | Command executed on the target device | # systemctl restart network |
## | Command executed inside a container on the target device | ## docker ps |
> | Command executed in the bootloader (e.g., U-Boot) | > printenv |
| (no symbol) | Output of a command | Login successful |
Notes on Command Execution
Commands in this section are shown with their respective execution context.
Always verify that you are operating on the correct device before running commands that affect system state.
If you are connected through SSH, make sure the target IP address corresponds to the intended Clea OS device before executing commands as root.