Skip to content
Clear Linux OS profile for Retail Node Installer
Branch: master
Clone or download
Fetching latest commit…
Cannot retrieve the latest commit at this time.
Type Name Latest commit message Commit time
Failed to load latest commit information.
conf RNC release 1.1 Dec 9, 2019
files/etc/systemd/network RNC release 1.1 Dec 9, 2019
licenses RNC release 1.1 Dec 9, 2019
syslinux RNC release 1.1 Dec 9, 2019
systemd RNC release 1.1 Dec 9, 2019
LICENSE RNC release 1.1 Dec 9, 2019 Update Dec 10, 2019 RNC release 1.1 Dec 9, 2019

Clear Linux OS Profile

Intended to be used with Retail Node Installer, this Clear Linux OS profile contains a few files that ultimately will install Clear Linux OS to disk.

Software Stack in this profile

  • Clear Linux

Target Device Prerequisites

  • x86 Bare Metal or x86 Virtual Machine
  • At Least 5 GB of Disk Space
    • Supports the following drive types:
      • SDD
      • NVME
      • MMC
  • 4 GB of RAM

Getting Started

A necessary prerequisite to using this profile is having an Retail Node Installer deployed. Please refer to Retail Node Installer project documentation for installation in order to deploy it.

Out of the box, the Clear Linux profile should just work. Therefore, no specific steps are required in order to use this profile that have not already been described in the Retail Node Installer documentation. Simply boot a client device using legacy BIOS PXE boot and the Clear Linux profile should automatically launch after a brief waiting period.

If you do encounter issues PXE booting, please review the steps outlined in the Retail Node Installer documentation and ensure you've followed them correctly. See the Known Issues section for possible solutions.

After installing Clear Linux, the default login username is sys-admin and the default password is P@ssw0rd!. This password is defined in the script and in the conf/config.yml as a kernel argument.

Kernel Paramaters used at build time

The following kernel parameters can be added to conf/config.yml

  • bootstrap - RESERVED, do not change
  • clearlinuxversion - Use the release number from here Defaults to latest release
  • debug - [TRUE | FALSE] Enables a more verbose output
  • httppath - RESERVED, do not change
  • kernparam - Used to pass additional kernel parameters to the targeted system. Example format: kernparam=splash:quiet#enable_gvt:1
  • parttype - RESERVED, do not change
  • password - Initial user password. Defaults to 'password'
  • proxy - Add proxy settings if behind proxy during installation. Example:
  • proxysocks - Add socks proxy settings if behind proxy during installation. Example:
  • release - [prod | dev] If set to prod the system will shutdown after it is provisioned. Altnerativily it will reboot.
  • token - GitHub token for private repositories, if this profile is in a private respository this token should have access to this repo
  • username - Initial user name. Defaults to 'sys-admin'

Known Limitations

  • Currently does not support full disk encryption
  • Currently does not install Secure Boot features


If you want to customize your Retail Node Installer profile, follow these steps:

  • Duplicate this repository locally and push it to a separate/new git repository
  • Make changes after reading the information below
  • Update your Retail Node Installer configuration to point to the git repository and branch (such as master).

The flexibility of Retail Node Installer comes to fruition with the following profile-side file structures:

  • conf/config.yml - This file contains the arguments that are passed to the Linux kernel upon PXE boot. Alter these arguments according to the needs of your scripts. The following kernel arguments are always prepended to the arguments specified in conf/config.yml:
    • console=tty0
    • httpserver=@@HOST_IP@@
    • bootstrap=http://@@HOST_IP@@/profile/${profileName}/
  • conf/files.yml - This file contains a few definitions that tell Retail Node Installer to download specific files that you can customize. Please check if there are any Known Limitations before changing this file from the default. See conf/files.sample.yml for a full example.
  • - A profile is required to have a as an entry point. This is an arbitrary script that you can control. If you plan to create profiles for other operating systems such as Ubuntu or Debian, it is recommended to use preseed to launch as the last step. Currently the following variables are processed:
    • @@DHCP_MIN@@
    • @@DHCP_MAX@@
    • @@HOST_IP@@
    • @@PROFILE_NAME@@

Customization Requirements

A profile must have all of the following:

  • a file at the root of the repository
  • a conf/files.yml specifying an initrd and vmlinuz, as shown in the conf/files.yml file.
You can’t perform that action at this time.