docker

Captured 2026-08-03 from one CE of this deployment.

Docker runs the platform services. Kubernetes workloads are under CRI-O.

docker-ps

{"command":["docker-ps"]}

CONTAINER ID   IMAGE                                              COMMAND                  CREATED             STATUS             PORTS     NAMES
f117f7fec5ed   gcr.download.volterra.io/volterraio/site-console   "container-entrypoin…"   About an hour ago   Up About an hour             site-console
6e922d6c5cd2   gcr.download.volterra.io/volterraio/vpm            "/bin/vpmd"              About an hour ago   Up About an hour             vpm
a89a93e00ed7   gcr.download.volterra.io/volterraio/argo           "/bin/bash -c 'sourc…"   About an hour ago   Up About an hour             argo_watch

Three containers is the whole list, not a broken node

vpm, argo_watch and site-console. Because most of the node runs under CRI-O, a short docker-ps looks like a failure if you are expecting Kubernetes workloads here. It is not — this is the complete set of Docker containers on a healthy CE, and vpm being present and Up is the single most important line on the page.

docker-ps-a

{"command":["docker-ps-a"]}

CONTAINER ID   IMAGE                                              COMMAND                  CREATED             STATUS             PORTS     NAMES
f117f7fec5ed   gcr.download.volterra.io/volterraio/site-console   "container-entrypoin…"   About an hour ago   Up About an hour             site-console
6e922d6c5cd2   gcr.download.volterra.io/volterraio/vpm            "/bin/vpmd"              About an hour ago   Up About an hour             vpm
a89a93e00ed7   gcr.download.volterra.io/volterraio/argo           "/bin/bash -c 'sourc…"   About an hour ago   Up About an hour             argo_watch

Includes exited containers, so a vpm that keeps dying leaves evidence here.

docker-images

{"command":["docker-images"]}

IMAGE   ID             DISK USAGE   CONTENT SIZE   EXTRA

The image tags identify the platform version the node is actually running, which is worth comparing against the software build reported by health.

docker-inspect

{"command":["docker-inspect","<container-id-or-name"]}

[
    {
        "Id": "f117f7fec5ed440b3eb6f2fed45cb26ea2ec83f93faedc312c33ed74216c3ccb",
        "Created": "2026-08-03T15:02:21.734985693Z",
        "Path": "container-entrypoint",
        "Args": [
            "npm",
            "run",
            "start-prod:site-console"
        ],
        "State": {
            "Status": "running",
            "Running": true,
            "Paused": false,
            "Restarting": false,
            "OOMKilled": false,
            "Dead": false,
            "Pid": 2403,
            "ExitCode": 0,
            "Error": "",
            "StartedAt": "2026-08-03T15:02:22.194718719Z",
            "FinishedAt": "0001-01-01T00:00:00Z"
        },
        "Image": "sha256:654314755ed88bed4ae872f63dc271809b5800817f5a6e91d82f3b6836917b25",
        "ResolvConfPath": "/var/lib/docker/containers/f117f7fec5ed440b3eb6f2fed45cb26ea2ec83f93faedc312c33ed74216c3ccb/resolv.conf",
        "HostnamePath": "/var/lib/docker/containers/f117f7fec5ed440b3eb6f2fed45cb26ea2ec83f93faedc312c33ed74216c3ccb/hostname",
        "HostsPath": "/var/lib/docker/containers/f117f7fec5ed440b3eb6f2fed45cb26ea2ec83f93faedc312c33ed74216c3ccb/hosts",
        "LogPath": "/var/lib/docker/containers/f117f7fec5ed440b3eb6f2fed45cb26ea2ec83f93faedc312c33ed74216c3ccb/f117f7fec5ed440b3eb6f2fed45cb26ea2ec83f93faedc312c33ed74216c3ccb-json.log",
        "Name": "/site-console",
        "RestartCount": 0,
        "Driver": "overlay2",
        "Platform": "linux",
        "MountLabel": "",
        "ProcessLabel": "",
        "AppArmorProfile": "",
        "ExecIDs": null,
        "HostConfig": {
            "Binds": [
                "/var/lib/vpm/data/certs/used/:/usr/src/apps/volterra/site-console/certs/:ro",
                "/tmp/debuginfo/:/usr/src/apps/volterra/site-console/debug_info:ro"
            ],
            "ContainerIDFile": "",
            "LogConfig": {
                "Type": "json-file",
                "Config": {
                    "max-size": "50m"
                }
            },
            "NetworkMode": "host",
            "PortBindings": {},
            "RestartPolicy": {
                "Name": "no",
                "MaximumRetryCount": 0
            },
            "AutoRemove": true,
            "VolumeDriver": "",
            "VolumesFrom": null,
            "ConsoleSize": [
                0,
                0

... [capture trimmed: first 60 of 261 lines]

Accepts a name as well as an id, so docker-inspect vpm works and is stable across restarts. Full JSON: mounts, environment, restart policy and the exit state.

docker-logs

{"command":["docker-logs","<container-id-or-name>"]}

> site-console@0.0.1 start-prod:site-console
> cd server;npm start


> stellar-webserver@1.0.0 start
> node index.js

CE is not provisioned, enabling all proxies.
8/3/2026, 3:02:23 PM || info: "Enabling http-basic-auth as required by config"
8/3/2026, 3:02:23 PM || info: "Serving static content from ../debug_info folder on endpoint /debug-info/files with index page enabled"
8/3/2026, 3:02:23 PM || info: "Same port passed for HTTP and HTTPS server (port 65500), disabling HTTP server then..."
8/3/2026, 3:02:23 PM || info: "HTTPS server started; port: 65500"
localhost : 200
8/3/2026, 3:39:56 PM || info: "password-verify exited with code: 200 / {\"username\":\"admin\",\"status\":true}"
8/3/2026, 3:39:56 PM || info: "Route /usr/src/apps/volterra/site-console/dist/site-console/, replacing with index.html"
localhost : 500
8/3/2026, 3:39:58 PM || info: "password-verify exited with code: 500 / {\"code\":13,\"details\":[{\"code\":\"UNKNOWN\",\"details\":\"Unable to validate current password for this user: admin\",\"timestamp\":\"2026-08-03T15:39:58Z\"}],\"message\":\"Unable to validate current password for this user: admin\"}"
localhost : 500
8/3/2026, 3:43:30 PM || info: "password-verify exited with code: 500 / {\"code\":13,\"details\":[{\"code\":\"UNKNOWN\",\"details\":\"Unable to validate current password for this user: admin\",\"timestamp\":\"2026-08-03T15:43:30Z\"}],\"message\":\"Unable to validate current password for this user: admin\"}"
localhost : 200
8/3/2026, 3:43:32 PM || info: "password-verify exited with code: 200 / {\"username\":\"admin\",\"status\":true}"
8/3/2026, 3:43:32 PM || info: "Route /usr/src/apps/volterra/site-console/dist/site-console/, replacing with index.html"
localhost : 500
8/3/2026, 3:43:33 PM || info: "password-verify exited with code: 500 / {\"code\":13,\"details\":[{\"code\":\"UNKNOWN\",\"details\":\"Unable to validate current password for this user: admin\",\"timestamp\":\"2026-08-03T15:43:33Z\"}],\"message\":\"Unable to validate current password for this user: admin\"}"

npm warn Unknown global config "python". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown env config "python". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
npm warn Unknown global config "python". This will stop working in the next major version of npm. See `npm help npmrc` for supported config options.
(node:28) MaxListenersExceededWarning: Possible EventEmitter memory leak detected. 11 close listeners added to [Server]. MaxListeners is 10. Use emitter.setMaxListeners() to increase limit
(Use `node --trace-warnings ...` to show where the warning was created)

docker-logs vpm is the fastest route to registration errors. For the same information with timestamps and across restarts, use journalctl instead.

docker-prune

execcli docker-prune

Removes every unused Docker object — stopped containers, unused networks, dangling images and build cache.

Only from the box. docker-prune is not on the debug API; it needs execcli.

Destructive, and not captured here

This deletes state. It is on the harvest harness’s refusal list and was never run, so this page documents it from the appliance’s own catalog metadata rather than showing output.

The CE-specific caution: this node runs two container runtimes. docker-prune touches only the Docker side — vpm, argo_watch and site-console — and cannot reach the Kubernetes workloads under CRI-O. Reclaiming space on the CRI-O side is a different command, systemctl-start-crio-prune, which is not present on this build.