status 및 doctor

ironflock status [flags]

# 로그인 계정으로 읽은, 이 머신에 있는 것
ironflock status
# 모든 정보를 JSON으로
sudo ironflock status --json
# SSH로 다른 머신의 상태 확인
ironflock --host pi@device-17 status

$ ironflock status
Agent:         installed in /opt/ironflock/device-agent
  Version:     1.6.9
  Service:     running (ironflock-device-agent.service)
  Connection:  unknown (this agent does not report it)
  Device:      unknown (needs root)
  Swarm:       unknown (needs root)
  Update:      none pending
Appliance:     not installed
System:        Debian GNU/Linux 12 (bookworm)

Run 'sudo ironflock status' to read what needs root.

System:        IronFlockOS 0.13.0 (amd64-efi, base)
  Image:       ironflockos-amd64-efi-base (build 20261105T120000Z-g1a2b3c4)
  Slot A:      inactive, good
  Slot B:      booted, good, 0.13.0 installed 2026-11-05T14:00:00Z
  Next boot:   slot B

Agent:         not enrolled yet: the device enrolls with a .flock on its IRONFLOCKOS partition at its next start, or now with 'sudo ironflock agent configure -c <file>'
Agent:         not to be seen: /data, which holds the agent and its .flock, could not be mounted (below); a .flock on the IRONFLOCKOS partition enrolls the device at its next start for as long as /data is missing

  Last reset:  gave up after 3 attempts at 2026-11-11T09:00:00Z: the data partition is not the partition named data on the disk of the root slot; /data holds the old data; left of the old owner: the data partition, the booted root slot, the other root slot
  Reset hold:  wait: a reset is open; a .flock or proxy.conf on the IRONFLOCKOS partition is not taken while the old owner's data may be on /data
  /data:       NOT MOUNTED: the device runs on the root slot's own folders; Docker and the apps do not run, and what is written now is lost with the next update
  /apps:       not the data partition's folder: the apps run, but lose their data at the next OS update

System:        Debian GNU/Linux 13 (trixie)
  OS install:  'ironflock os install' stopped at 2026-11-11T10:00:00Z before it wrote the disk: the disk /dev/sda is not the plan's: its size changed from 64.0 GB to 32.0 GB; nothing was changed, and this system runs as before

{
  "agent": {
    "installed": true,
    "layout": "current",
    "dir": "/opt/ironflock/device-agent",
    "version": "1.6.9",
    "service": {"unit": "ironflock-device-agent.service", "state": "running"},
    "connection": "unknown",
    "device": "demo-device",
    "swarm": "demo_swarm",
    "update": {"state": "none"}
  },
  "appliance": {"installed": false},
  "os": {"name": "Debian GNU/Linux 12 (bookworm)", "id": "debian", "version": "12", "ironflockos": false},
  "needs_root": []
}

ironflock doctor [flags]

# 로그인 계정으로 이 머신 검사
ironflock doctor
# root로 모든 항목을 검사하고 JSON으로 출력
sudo ironflock doctor --json
# .flock을 설치하기 전에 그 호스트 검사
ironflock doctor -c device.flock

$ sudo ironflock doctor
Download base: https://instance-registry.ironflock.com/dl
Device file:   /opt/ironflock/device-agent/device-config.flock

CHECK            RESULT  FINDING
privileges       ok      runs as root
system           ok      Debian GNU/Linux 12 (bookworm), amd64
systemd          ok      systemd runs this system
docker           ok      Docker 27.3.1 runs
disk_space       ok      50.0 GB free for /opt and /var
clock            ok      within 10 s of the download server's clock
dns              ok      resolves instance-registry.ironflock.com, cbw.ironflock.com, europe-docker.pkg.dev
proxy            ok      none: the connections go direct
download_tree    ok      https://instance-registry.ironflock.com/dl has the agent 1.6.9 for amd64
device_endpoint  ok      cbw.ironflock.com answers
docker_registry  failed  europe-docker.pkg.dev cannot be reached: no answer within 20 s
update_server    ok      https://instance-registry.ironflock.com/dl has the agent's updates

What to do:
  docker_registry: the device pulls its apps' images from there: let this machine reach europe-docker.pkg.dev on port 443, directly or through the proxy

Failed: docker_registry.

Download base: http://10.0.0.5:15002/dl (the appliance's mirror of the .flock; the IronFlock cloud for what it does not give)

{
  "result": "failed",
  "checks": [
    {"id": "privileges", "result": "ok", "finding": "runs as root"},
    {"id": "docker_registry", "result": "failed", "finding": "europe-docker.pkg.dev cannot be reached: no answer within 20 s", "hint": "the device pulls its apps' images from there: let this machine reach europe-docker.pkg.dev on port 443, directly or through the proxy"}
  ],
  "download_base": "https://instance-registry.ironflock.com/dl",
  "flock": "/opt/ironflock/device-agent/device-config.flock"
}