pixop-version

Print baked appliance identity from /etc/pixop-live/ami-build.env. Use this to match procurement records, support tickets, and documentation to the image actually running — not to PIXOP_MARKETPLACE_AMI_VERSION, which can differ from the bake file and affects activation reporting only.

Availability: Verify with command -v pixop-version on your installed appliance when this guide applies to your deployment. Installed path when present: /opt/pixop/bin/pixop-version.

Purpose and scope

Answers: which Pixop appliance build is on disk, when it was baked (UTC), which digest-pinned Pixop LIVE image the recipe recorded, and whether provenance came from AWS Image Builder. The command is read-only: it does not start services, call AWS, or read instance metadata.

Build origin AWS Image Builder means the image was produced in Image Builder (including a KVM QCOW2 exported from that bake). It does not assert the host is EC2. Workbenches or hosts without a readable bake file show unknown for missing fields.

Usage

pixop-version [--json] [--verbose]

Flag	Behavior
(none)	Human-readable four-line summary
`--json`	`{"version", "build_time_utc"}` only; missing values are JSON `null`
`--verbose`	Extra bake metadata on stdout (human only): git commit, TSDuck image, NVIDIA driver branch, container toolkit, base image file, base AMI ID
`-h` / `--help`	Usage text

Privileges: No sudo. Runs as any user who can read ami-build.env (typically world-readable on the appliance).

Exit codes: 0 on success (including missing bake metadata). 2 for unknown options.

Interpreting output

Label (text mode)	Source key	Notes
Pixop appliance version	`AMI_VERSION`	AMI recipe version string from your build
Build origin	file presence	`AWS Image Builder` if the env file exists and is readable; else `unknown`
Built (UTC)	`BUILD_TIME_UTC`	Bake timestamp
Pixop LIVE	`PIXOP_LIVE_IMAGE`	Digest-pinned image reference from bake

--json does not include LIVE image, build origin, or verbose fields — use text or --verbose when you need those.

Operator workflows

After launch or KVM import — confirm build:

pixop-version

Automation / monitoring hook (version + bake time only):

pixop-version --json

Support ticket header (non-secret provenance):

pixop-version --verbose

Compare with Overview release table and your contract; do not assume git main matches the guest.

Troubleshooting

Situation	Meaning
All fields `unknown`	No readable `/etc/pixop-live/ami-build.env` (custom image, incomplete install, or pre-bake workbench)
Version mismatch vs Marketplace console	Expected if `PIXOP_MARKETPLACE_AMI_VERSION` was overridden; trust `pixop-version` for the bake
`--verbose` shows unexpected `BASE_AMI_ID`	Engineering audit trail only; customer upgrades use pixop-image-update

Limitations

Does not report running Docker digests, license state, or SRT configuration.
Does not detect drift if an operator replaced images without rebaking.
KVM guests exported from Image Builder retain the same bake file as the source AMI.

Monitoring and troubleshooting — what to send support
pixop-preflight — host readiness after you know the build
pixop-image-update — change Pixop LIVE image on a launched instance
KVM deployment guide — QCOW2 recipe vs Marketplace version