Skip to content
Librux Runtime Kernel for Robotics development
Librux Runtime Kernel for Robotics development

    Quickstart

    Use this page for the first run after installing Librux. The goal is simple. confirm the installed runtime, prepare your Python environment, open the local Web Console, and choose the next path.

    1. Install Librux

    Complete Installation first.

    The default install prefix is this.

    /opt/librux

    Default install output includes the following.

    • runtime under /opt/librux/runtime
    • SDK payloads under /opt/librux/sdk
    • tutorials under /opt/librux/tutorials
    • benchmarks under /opt/librux/benchmarks
    • license and notice documents under /opt/librux/licenses

    Source the installed environment helper in each shell that will run Librux commands.

    . /opt/librux/env.sh

    2. Check Python SDK Availability

    Ubuntu / Debian.

    sudo apt update
sudo apt install -y python3-venv python3-pip

    The installer places the Python SDK wheel and an unpacked managed-package runtime under /opt/librux/sdk/python. After sourcing env.sh, installed tutorial packages and managed Python packages can import the SDK without a separate source checkout.

    . /opt/librux/env.sh
python3 -c 'import librux; print("Librux Python SDK ready")'

    Use a virtual environment only when you want an isolated development shell.

    python3 -m venv librux-quickstart
. librux-quickstart/bin/activate
. /opt/librux/env.sh
python -m pip install /opt/librux/sdk/python/librux_client-*.whl

    You do not need an SDK source checkout for normal installed tutorial or benchmark runs.

    3. Check The Control Backend

    If librux-control.service was installed.

    sudo systemctl status librux-control.service --no-pager

    The important line is Active: active (running). The service uses /opt/librux/runtime/config.yaml by default, where the bundled Web Console and HTTP API listen on port 8001.

    Check readiness.

    curl -sf http://127.0.0.1:8001/api/v1/ready

    Open the local Web Console.

    http://127.0.0.1:8001/

    If your browser is running on a different machine, replace 127.0.0.1 with the runtime host address. Do this only on a trusted network or after enabling Web/API security.

    If systemctl status also shows pmc ... bind failed: Permission denied line, that message is from linuxptp time-sync telemetry, not from the Web Console itself. Check the dedicated time-sync service separately.

    sudo systemctl status librux-timesyncd.service --no-pager
librux timesync doctor

    4. If Services Were Skipped

    Some tutorial and package flows require the resource service. If installation skipped system services, register them before running managed packages.

    sudo /opt/librux/bin/librux system install \
  --prefix /opt/librux

    For cross-host or site-specific configs.

    sudo /opt/librux/bin/librux system install \
  --prefix /opt/librux \
  --config /path/to/config.yaml

    For time-sync details, use Time Sync Operations.

    5. Continue

    After the first install check, continue in this order. Tutorial and benchmark checks are covered on the pages that use them.

    1. Operate - service status, Web Console, resource control, time sync, security, and deployment checks.
    2. Develop - the cleaner robot tutorial and subsystem/package development workflow.
    3. Performance - benchmark tracks and measurement rules.

    Clone source repositories only when you need editable source work.

    • clone librux-sdk for editable SDK development, source-level SDK tests, or advanced benchmark matrix tooling
    • use the entry repository's librux.repos manifest when you need the matching SDK and docs source workspace
    • clone librux-demo separately when you want complete robotics application demos