mirror of
https://github.com/Katakate/k7.git
synced 2026-11-20 20:34:24 +00:00
Observability, usage metering, tenants and quotas, and roles with OIDC login. A Helm chart installs K7 on a cluster you already run, API keys carry a role, and k7-agent no longer needs host privileges.
800 B
800 B
K7dDaemonDown
The k7-agent on instance cannot connect to the k7d control socket
(/run/k7d/k7d.sock). k7d sandboxes on that node cannot be created,
paused, resumed or forked.
First three commands
ssh <node> systemctl status k7d --no-pager
ssh <node> journalctl -u k7d --since -30min --no-pager | tail -50
ssh <node> ls -l /run/k7d/
Reading them
inactiveorfailed: start it withsystemctl restart k7dand read the journal for the cause. A version mismatch with/etc/k7/k7d_versionmeans the node needsk7 installagain.activebut no socket: k7d is still starting, or it failed to bind. The journal says which.- The socket exists and the alert still fires: the agent pod lacks the
/run/k7dhostPath mount. Re-runk7 installorhelm upgrade.