Blueforce-Linux/provisioning/offline-repo/manifests/docker.txt
emirhanmamak-blueforce ef102b9657 feat(field-os): provisioning layer, real ISO build, offline contracts
Adds the Blueforce Field OS provisioning stack on top of the existing fleet
architecture, without rewriting the working systems (installer, diagnostics,
Ansible, WireGuard/SSH/xRDP/RustDesk, Docker policies, monitoring, Docusaurus).

ISO build (the previous builder was a skeleton that produced no medium):
- boot layout is read from the base ISO at build time via
  `xorriso -report_el_torito as_mkisofs` and rebuilt with `-as mkisofs`;
  `-boot_image any replay` cannot work on Ubuntu live ISOs because the GRUB2
  MBR lives in the source image's first 16 sectors and the EFI system partition
  is an appended partition, neither of which is a file in the ISO9660 tree
- preflight now asserts El Torito boot metadata positively: xorriso exits 0 on
  a non-ISO input, which previously let an arbitrary file pass --check
- artifact produced and verified: dist/Blueforce-Field-OS-1.0.0-amd64.iso,
  6 481 917 952 bytes, SHA256 cb0cc56f...d431296, BIOS+UEFI entries preserved,
  /autoinstall.yaml at the media root, casper/minimal.squashfs byte-identical
  to the base
- recorded baseline deviation: the verified medium on the build host is the
  Desktop flavour, so the manifest carries a baseline_deviation block instead
  of hiding it; Server remains one flag away

Offline and identity:
- offline APT contract with concrete package requirements, pin format and an
  audit table; builds fail closed while pins are UNPINNED
- autoinstall keeps interactive-sections: [storage]: the operator confirms the
  target disk, and no automatic wipe is ever performed
- firstboot terminal wizard for the 8-digit dealer id, three-state lifecycle
  (PROVISIONED_OFFLINE -> ENROLLED -> READY) with fail-closed gates, so a
  missing internet link or WireGuard handshake cannot fail provisioning but can
  never produce a false READY

Fleet and migration:
- five read-only Ansible playbooks for Field OS version, provisioning,
  enrollment, remote channels and offline readiness, all wave-scoped with a
  separate production override
- Windows pre-migration inventory and data export extended to the full brief
  scope, read-only, never collecting credentials

Tests: tests/run-all.sh -> 8/8 pass, exit 0. Boot acceptance (UEFI, Legacy
BIOS, Secure Boot), air-gapped install, real enrollment endpoint and Windows
rollback remain LAB work and are listed in IMPLEMENTATION-REPORT.md.
2026-09-16 11:14:42 +03:00

30 lines
1.7 KiB
Text

# Blueforce Field OS - offline APT pin manifest: Docker CE
#
# Target release : Ubuntu 26.04 LTS, architecture amd64 (LAB confirms both)
# Format : one exact pin per line -> package=version ("#" starts a comment)
# Consumed by : scripts/install/blueforce-install.sh --offline, which refuses to
# run any package module unless every pin here is present in the
# bundle lock file <repo>/packages.lock.tsv.
#
# UNPINNED is a sentinel, not a version. Fill it in LAB:
# 1. acquire the reviewed .deb for the package into one local pool directory
# 2. read the exact version: dpkg-deb -f <file>.deb Package Version
# 3. replace UNPINNED with that version, keeping the line shape:
# docker-ce=<exact version reported by dpkg-deb>
# 4. verify with the static plan: ../build-offline-repo.sh --dry-run-plan
# (it must print PLAN READY before --check or a real build is attempted)
#
# Rules enforced by the tooling: lower-case package names, exactly one pin per
# package across all manifests, no inline comments, no whitespace around "=",
# no placeholder/replace/todo tokens. Adding or removing a package is a contract
# change: update manifests/requirements.tsv in the same edit or the plan fails.
# These packages are NOT in the Ubuntu archive: they come from the reviewed Docker
# CE repository snapshot and must be supplied as local .deb files. containerd.io is
# the runtime bundled with Docker CE, not Ubuntu's "containerd" package.
# Installer module 10-docker.sh installs exactly this set in --offline mode.
docker-ce=UNPINNED
docker-ce-cli=UNPINNED
containerd.io=UNPINNED
docker-buildx-plugin=UNPINNED
docker-compose-plugin=UNPINNED