AtomOS Docs

Appearance

Quick start — first deployment ​

End-to-end path from a prepared Linux host to a verified AtomOS node and a first VM via Electros. Adjust roles and networking for your topology (Planning, Architecture).

Safety first

  • Keep BMC, IPMI, or physical console access before changing networking.
  • Do not put your only management NIC on br0 without a recovery path (Networking).
  • Docs revision 2026-10-25 — confirm package behavior with atomos-cli --version on the host; no fixed stable version is asserted here.

1. Prerequisites ​

CheckAction
Supported host OSClean install; see Hardware & platforms
VirtualizationCPU VT-x/AMD-V enabled in firmware
Root/sudoInstall requires root
Outbound HTTPSRepositories and repo.elemento.cloud reachable (install reference)
LicenseValid Elemento license file when prompted
Network planDedicated NIC for guest bridge vs management

On cloud instances:

bash
# After bootstrap only — example post-install check documented in install guide
sudo atomos-cli --verify-network

Run --verify-network after atomos-cli exists (step 2).

2. Bootstrap atomos-cli (download, then execute) ​

Prefer download-then-execute over piping curl directly into a shell:

bash
curl -fsSL https://repo.elemento.cloud/get-atomos.sh -o /tmp/get-atomos.sh
chmod +x /tmp/get-atomos.sh
sudo /tmp/get-atomos.sh

The script installs /usr/bin/atomos-cli and configures periodic update checks. From the published 0.9 milestone onward the CLI is atomos-cli (formerly nucleus).

3. Choose and install a role (on-prem examples) ​

Hyperconverged lab (compute + storage):

bash
sudo atomos-cli --install full on-prem

Compute-only node (remote vaults):

bash
sudo atomos-cli --install compute on-prem

Dedicated storage node:

bash
sudo atomos-cli --install storage on-prem

Optional local UI (0.9+ milestone):

bash
sudo atomos-cli --install atomosgui on-prem

For provider instances with nested virtualization, replace on-prem with cloud as documented in Install with atomos-cli.

Bridge prompt during install

Install may prompt for a NIC and create br0 via NetworkManager. Select the guest/data NIC, not your only management interface.

4. Bridge (if not done during install) ​

bash
sudo atomos-cli --bridge-setup
sudo atomos-cli --verify-network

5. Vault (storage role or full) ​

bash
sudo atomos-cli --vault-creator
sudo atomos-cli --restart storage

Default example mount: /mnt/elemento-vault/. See Storage architecture.

6. TLS certificates (HTTPS from 0.9 milestone) ​

Generate a certificate covering every IP and DNS name used to reach the host:

bash
sudo atomos-cli --generate-cert
sudo atomos-cli -ra
sudo atomos-cli --show-fingerprint

7. Verify installation ​

bash
sudo atomos-cli --verify-install
sudo atomos-cli --info
sudo atomos-cli --healthcheck

Optional modules:

bash
sudo atomos-cli --modules

8. Connect Electros or use AtomOS GUI ​

Electros (fleet):

  1. Organisation admin: Connections → Targets → Add AtomOS.
  2. Enter target name and host IP (reachable on HTTPS).
  3. Compare fingerprint with sudo atomos-cli --show-fingerprint on the host; approve only if it matches.
  4. Active Connections — enable the target or scenario.

Walkthrough: VMs & Electros and Electros Connections.

AtomOS GUI (on-host): browse to GUI ports listed in install reference after atomosgui install; manage local users with sudo atomos-cli -mu.

9. Create a VM (Electros documented flow) ​

Do not rely on undocumented UI fields — follow Electros product docs:

  1. IaaS → Virtual Machines — define guest, volumes, networks (Virtual machines user guide).
  2. Review → Continue → Choose a Host → Create (or automatic selection when enabled).
  3. Open console (VNC), install guest OS, validate network and storage.

CPU/memory changes and attachments: Live resource changes (provisional guest matrix).

10. Post-deploy checks ​

bash
sudo atomos-cli --status
sudo atomos-cli --logs

From another host, confirm Electros shows healthy inventory and expected capacity.

Where to go next ​