Hauler Login

Overview

hauler login authenticates to an OCI-compliant registry and saves the credentials to the standard Docker config at ~/.docker/config.json.

Run it before any Hauler operation that talks to a protected registry. On the connected side that means pulling private images with hauler store add image or hauler store sync; on the airgapped side it means seeding a secured registry with hauler store copy. Hauler reads the same credential store that Docker and other OCI tools use, so a login you've already performed with docker login works too, and vice versa. For scripts and CI, prefer --password-stdin over --password so the secret never appears in your shell history or process list.

An example with available flags...

hauler login <registry-url> --username <username> --password <password>

# read the password from stdin instead of the command line
echo "$REGISTRY_PASSWORD" | hauler login <registry-url> --username <username> --password-stdin

Command Overview

Usage:
  hauler login [OPTIONS] [SERVER] [flags]

Examples:
  # Log in to reg.example.com
  hauler login reg.example.com -u AzureDiamond -p hunter2

Flags:
  -h, --help              help for login
  -p, --password string   Password
      --password-stdin    Take the password from stdin
  -u, --username string   Username

Global Flags:
      --audit-level string   Set the audit logging level (none, standard, verbose) (defaults standard)
  -d, --haulerdir string     Set the location of the hauler directory (default $HOME/.hauler)
      --ignore-errors        Warn and continue instead of failing on errors, including storing images that failed verification (defaults false)
  -l, --log-level string     Set the logging level (i.e. info, debug, warn) (defaults info)
  -w, --work-dir string      (Optional) Set the directory for output that commands would otherwise write to the current directory (default: current directory)