Skip to content

BeforeUp 0.4.4

Latest

Choose a tag to compare

@BreezeDelegate BreezeDelegate released this 02 Nov 14:06
· 1 commit to main since this release

BeforeUp 0.4.4

BeforeUp 0.4.4 adds read-only warnings for Docker Compose configurations that pass schema validation but can fail or behave differently when started.

New diagnostics

  • RESTART_POLICY_OVERRIDDEN: an incomplete deploy restart policy can silently replace an explicit service restart policy.
  • RESTART_POLICY_INVALID: a positive retry limit without a compatible on-failure condition can cause container creation to fail.
  • PRE_START_REPLICA_UNSUPPORTED: a per-replica pre-start hook is accepted by Compose configuration validation but rejected at startup.

These warnings apply only to Docker Compose 5.5.0, 5.5.1, 5.6.0 and 5.6.1, independently reproduced on Debian 13 amd64 with rootful Docker Engine 29.8.1. Other Compose versions are not classified by these checks. Warnings do not block by default; --strict can make them fail a CI preflight.

Verification. Go tests, race checks, vet and formatting checks passed. The 14-case existing Compose matrix and 56 targeted read-only cases across four Compose versions passed. The amd64 Debian package installed, ran and was removed in isolated Debian 13, Ubuntu 24.04 and Ubuntu 26.04 containers. The ARM64 assets were cross-built and were not tested on ARM64 hardware.

Install. Download the matching archive or Debian package below and verify its SHA-256 checksum against SHA256SUMS before installing.

  • Debian/Ubuntu amd64: sudo apt install ./beforeup_0.4.4_amd64.deb
  • Other Linux installations: unpack the matching archive after checksum verification.
  • Commands: beforeup check -f compose.yaml or beforeup compare -f compose.yaml.

BeforeUp does not start or reconfigure containers. A clean preflight is not proof of successful startup or application health. SELinux-enforcing, rootless writable mounts, Docker Desktop and ARM64 Docker Engine integration remain unverified.