Skip to content

Installation

For macOS and Windows platform notes, see platforms.

Build from source

make build

Platform binaries are written under release/ (for example release/syver-linux-amd64).

Install a built binary on your PATH:

cp release/syver-linux-amd64 /usr/local/bin/syver   # adjust OS/arch as needed
chmod +rx /usr/local/bin/syver

Build a single platform target:

make release/syver-linux-amd64

Alternatively, build with GoReleaser:

goreleaser build --clean --single-target --snapshot

The binary is written under dist/, in a directory named for the build id in .goreleaser.yaml -- currently binaries, so for example dist/binaries_linux_amd64_v1/syver.

dgoss and other wrappers

  • dgoss — run goss against Docker/Podman containers
  • kgoss — Kubernetes wrapper
  • dcgoss — Docker Compose wrapper
  • sbxsyver — Docker Sandboxes (sbx) wrapper

Release binaries

The supported install path is:

curl -fsSL https://raw.githubusercontent.com/krameff/syver/main/install.sh | sh

Release assets are raw, uncompressed binaries named syver-<os>-<arch> (for example syver-linux-amd64; Windows builds are named syver-windows-amd64.exe). The goss-named binaries were last published with v0.9.1.

To install manually from a GitHub release:

SYVER_VER=v0.15.0   # any tag from the Releases page
curl -L "https://github.com/krameff/syver/releases/download/${SYVER_VER}/syver-linux-amd64" \
  -o /tmp/syver
sudo mv /tmp/syver /usr/local/bin/syver
chmod +rx /usr/local/bin/syver

Adjust the version, OS, and architecture in the filename as needed. Release binaries are 64-bit only: linux has amd64, arm64, s390x and ppc64le, darwin has amd64 and arm64, and windows has amd64. On a 32-bit system, build from source.

Verifying release signatures

Each release's SHA256SUMS checksum file is GPG-signed with the project's signing key (fingerprint CD218D529C95DC65A71F18D84C9E5095CABE5092, published as krameff-syver-key.asc at the repo root and attached to every release).

SYVER_VER=v0.15.0   # the release you downloaded

# import the signing key once
curl -fsSL https://raw.githubusercontent.com/krameff/syver/main/krameff-syver-key.asc | gpg --import

# download the checksum file and its signature from the release page, then:
gpg --verify syver_${SYVER_VER#v}_SHA256SUMS.sig syver_${SYVER_VER#v}_SHA256SUMS
# --ignore-missing: the file lists every release asset, not only the one you downloaded
sha256sum --ignore-missing -c syver_${SYVER_VER#v}_SHA256SUMS

A gpg --verify output of Good signature from "Krameff Solutions Limited..." confirms the checksum file (and therefore every archive listed in it) came from this project and hasn't been tampered with.