`pg_hardstorage demo` not doing anything

[Wolfsrudel]

What happened

I am running docker via lima, having a different socket than the default. Docker is working and environment variable is set as well.

$env.DOCKER_HOST = "unix:///Users/tobias.wolf/.lima/docker/sock/docker.sock"

docker container ls
CONTAINER ID   IMAGE                               COMMAND                  CREATED       STATUS          PORTS     NAMES
0bcd96dd9c54   registry.dagger.io/engine:v0.21.6   "dagger-entrypoint.s…"   13 days ago   Up 10 seconds             dagger-engine-v0.21.6

But the demo command is just producing an output, see:

pg_hardstorage demo
{
  "message": "pg_hardstorage demo — requires Docker, runs PG 18, cleanup automatic"
}

To reproduce

pg_hardstorage demo

pg_hardstorage version

pg_hardstorage 1.0.4 (6bf20a6, built 2026-06-24T20:10:58Z)

Doctor report

pg_hardstorage doctor
Mode: user

PATHS
  Config         /Users/tobias.wolf/.config/pg_hardstorage          [xdg] missing
    drop-in      /Users/tobias.wolf/.config/pg_hardstorage/conf.d   [derived] missing
    deployments  /Users/tobias.wolf/.config/pg_hardstorage/deployments [derived] missing
    sinks        /Users/tobias.wolf/.config/pg_hardstorage/sinks    [derived] missing
    skills       /Users/tobias.wolf/.config/pg_hardstorage/skills   [derived] missing
    keyring      /Users/tobias.wolf/.config/pg_hardstorage/keyring  [derived] missing
  State          /Users/tobias.wolf/.local/share/pg_hardstorage     [xdg] missing
    bookkeeping  /Users/tobias.wolf/.local/share/pg_hardstorage/bookkeeping [derived] missing
    inflight     /Users/tobias.wolf/.local/share/pg_hardstorage/inflight [derived] missing
    crashes      /Users/tobias.wolf/.local/share/pg_hardstorage/crashes [derived] missing
  Cache          /Users/tobias.wolf/.cache/pg_hardstorage           [xdg] missing
  Logs           /Users/tobias.wolf/.local/state/pg_hardstorage     [xdg] missing
  Runtime        /run/user/502/pg_hardstorage                       [xdg] missing
  Shared data    /Users/tobias.wolf/.local/share/pg_hardstorage/share [xdg] missing

CONFIG
  Status:        not yet configured
  Suggested:     pg_hardstorage init
  Source files:
    [absent ] /Users/tobias.wolf/.config/pg_hardstorage/pg_hardstorage.yaml

KEYSTORE
  Dir:           /Users/tobias.wolf/.config/pg_hardstorage/keyring
  Signing key:   ✗ absent
  KEK:           ✗ absent (backups will be unencrypted; run `init --encrypt` to provision)

AIRGAP
  Mode:          off

ISSUES
  [NOTICE] keystore.signing_key_absent: no signing keypair at /Users/tobias.wolf/.config/pg_hardstorage/keyring — backups will generate one on first run
    hint: run `pg_hardstorage init` to provision the keyring + KEK + signing keypair

Logs

n/a

Environment

• OS: MacOS 26.5.1
• Architecture: arm64
• PG: demo
• Repo backend: demo
• Coordination: demo

Anything else

Documentation says:

90-second demo
Bring up a temporary PostgreSQL 18 and run the full backup/restore/verify flow in Docker:
pg_hardstorage demo
The demo prints progress and a result summary. No existing PostgreSQL or pg_hardstorage configuration is needed — just a running Docker daemon.

[postgresql007]

Thanks for flagging this — and sorry for the confusing first impression. You did everything right; the command was at fault.

The honest answer is demo was a placeholder: it printed that one-line summary and exited without ever starting anything. That's squarely on us, especially with the docs promising a full backup/restore/verify run.

It's now implemented for real — it starts a throwaway PostgreSQL in Docker, initialises a repo, takes a backup, restores it, verifies it, and cleans up after itself, printing progress as it goes. It runs through your docker CLI, so your Lima setup with the custom DOCKER_HOST is picked up automatically — no extra config needed. And if Docker genuinely isn't reachable, you'll now get a clear error pointing at DOCKER_HOST instead of a silent "success".

Fix is in #18; I'll comment here again once it's merged and in a release so you can give it another spin. Thanks for trying it out and reporting back!