Coblyn quick start

●  Quick start⏱ 10 minv1.17.0 Release GateLast rev · 27 Jun 2026

Coblyn v1.17.0 "Release Gate" installs as a Docker appliance. This page starts a Web/API PoC without touching DHCP/PXE; for production, follow the full installation and operations guide.

Minimum requirements

• Operating system — Ubuntu Server 24.04 LTS amd64 or Debian 12 amd64.
• Permissions — sudo access.
• Network — Physical or bridged NIC if you will test DHCP/PXE.
• PoC resources — 4 vCPU, 8 GB RAM and 60 GB disk.
• Internet — Required to download the release, packages, and Docker images.

Verified download

install -d -m 0700 "$HOME/coblyn-bootstrap"
cd "$HOME/coblyn-bootstrap"
curl --proto '=https' --tlsv1.2 -fSLO \
  https://get.coblyn.gksistemas.es/releases/download/v1.17.0-rc.5/setup.sh
curl --proto '=https' --tlsv1.2 -fSLO \
  https://get.coblyn.gksistemas.es/releases/download/v1.17.0-rc.5/setup.sh.sha256
sha256sum --check setup.sh.sha256
less setup.sh

Do not execute a network response directly with curl | sudo bash. The less step lets you inspect what will run. The checksum detects corruption or an inconsistent download. Every release also includes a signed Sigstore manifest, but this remains a pilot channel until the bootstrap enforces that verification and a mirror exists outside the VPS.

PoC without DHCP/PXE

Run the interactive installer with the testing profile:

sudo bash ./setup.sh --release 1.17.0-rc.5 --testing --wizard

The bootstrap installs Coblyn under /opt/coblyn, prepares dependencies, generates safe secrets, and creates the first administrator with hidden input. The testing profile does not enable DHCP, PXE, or TFTP.

Validate the node

cd /opt/coblyn/coblyn
sudo ./setup.sh doctor
docker compose ps

If doctor detects old secrets or placeholders:

sudo ./setup.sh doctor --fix
sudo ./setup.sh doctor

First access

Open:

http://<PXE_SERVER_IP>:<WEB_PORT>

The interactive installer creates the first persistent administrator with hidden input. If you started the stack manually, run sudo ./setup.sh admin-bootstrap. The password is never stored in .env.

Next step

• Storage Hub — Configure an NFS or SMB/CIFS pool from Storage. Do not use the old NFS_SERVER/NFS_PATH model as the main source of truth.
• Boot assets — Upload boot assets under tftpboot/.
• PXE — Test a client on the correct VLAN.
• Backup — Before upgrades, run sudo ./setup.sh backup.

Full guide

For firewall, required secrets, v1.x upgrade and Alembic baseline, continue with Installation and operations.