Packages and mirrors

Every place Levelrail is published, how to check what you downloaded, and what exists today for networks where github.com is slow.

npm: levelrail-cli

The levelrail-cli package puts the command line client on any machine with Node.js. Pick the runner you already use.

  • Run once with npx
    npx levelrail-cli
  • Install globally with npm
    npm i -g levelrail-cli
  • Run once with Yarn
    yarn dlx levelrail-cli
  • Run once with pnpm
    pnpm dlx levelrail-cli

Client only. This package never installs the server. The server installs with the install script.

Platform packages

levelrail-cli pulls in the one matching your machine. You do not install these by hand.

Platform packages published with levelrail-cli
PackagePlatform
levelrail-cli-linux-amd64Linux, x86-64
levelrail-cli-linux-arm64Linux, ARM64
levelrail-cli-darwin-amd64macOS, Intel
levelrail-cli-darwin-arm64macOS, Apple silicon
levelrail-cli-windows-amd64Windows, x86-64
levelrail-cli-windows-arm64Windows, ARM64

Other ways to get it

  • The CLI for macOS and Linux, from the glincker tap.

    brew install glincker/tap/levelrail-cli
    glincker/homebrew-tap
  • CLI, agent and control plane binaries, .deb and .rpm packages for the agent, checksums.txt and its cosign bundle.

    Releases on GitHub
  • The control plane and the node agent, published to the GitHub Container Registry.

    docker pull ghcr.io/glincker/levelrail
    levelrail on ghcr.io
  • The server install. Checks the host, installs Docker if needed and verifies what it downloads.

    curl -fsSL https://levelrail.com/install.sh | sudo sh
    Install guide

The agent image is ghcr.io/glincker/levelrail-agent. Both images are tagged with the release version.

Mirrors and regions

github.com, ghcr.io and Docker Hub can be slow or blocked in some regions. The docs page Install from mainland China lists the settings for installing through other hosts while keeping the checksum and signature checks. The mirror variables it describes arrive in v0.9.4, and earlier releases do not read them.

Speed from mainland China has not been tested yet. Nothing on this page is a measured result.

Levelrail does not run its own mirrors today. Any third party mirror you use, such as a public registry proxy, is unofficial and community run. It is not operated or endorsed by the project, so rely on the checksum and signature checks, not on the mirror.

Trust and verification

  • Provenance. levelrail-cli is published to npm with a provenance attestation, so npm can show which repository and workflow built it.
  • Checksums. Every release lists the SHA-256 of each binary and install script in checksums.txt. The installer checks it for you.
  • Cosign. checksums.txt is signed keyless with cosign by the release workflow, and the container images are signed the same way.

The Verify a release guide has the exact cosign, checksum and attestation commands.