Installation verification

After installing Wave with any method, confirm the service is live and provisions containers. Run the liveness check first, then the functional checks for your configuration.

Check the service is live

Wave exposes /service-info. A healthy service returns its version and commit ID:

curl -s https://wave.example.com/service-info

{
  "serviceInfo": {
    "version": "1.34.0",
    "commitId": "a1b2c3d"
  }
}

If this returns a connection error, check that the service is running and that your ingress or load balancer routes to it. If it returns the wrong version, confirm the deployed image tag.

Install the Wave CLI

The functional checks use the Wave CLI.

# Homebrew
brew install seqeralabs/tap/wave-cli

# Or download a binary from the releases page
# https://github.com/seqeralabs/wave-cli/releases

Point the CLI at your service with the --wave-endpoint flag or the WAVE_API_ENDPOINT environment variable:

export WAVE_API_ENDPOINT=https://wave.example.com

note

If you disabled anonymous access in Configure Wave, the CLI checks need a Seqera Platform access token. See the wave-cli documentation for the token option.

Functional checks

Wave Lite

Augment an existing image. Wave should return an augmented image reference served by your deployment:

wave -i ubuntu:22.04

A successful augmentation prints a Wave image reference pointing at your service host.

Wave

In addition to the augmentation check above, verify the build features you enabled.

Build a container from a Conda package:

wave --conda-package bcftools

Build from a Dockerfile and freeze it to a persistent repository:

wave --containerfile Dockerfile --freeze --build-repo <build-repo>

A successful build returns a reference in your configured build repository.

If a check fails

If a check does not pass, match the symptom to one of these common causes:

• Augmentation or build fails with an authentication error: Wave cannot authenticate to the target registry. See Registry push and authentication failures.
• Build fails partway through a push: The target repository may not exist or may lack push scope. See per-registry pre-creation rules.
• Freeze is rejected even with a build repository set: The repository sits inside an operator-reserved prefix. See Freeze and user-supplied build repositories.

Next step

When the checks pass, continue to Configure Wave to harden the deployment for production.