Nora v1.16.4 — safer Remote Docker revocation and fail-closed recovery #290
solomon2773
announced in
Announcements
Replies: 0 comments
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Remote Docker security and lifecycle patch: revoking a workspace grant now
tears down Nora-mediated access that is already in flight, not only the next
request, while cleanup retains enough authority to avoid orphaning workloads.
Operator-facing changes
gateway RPCs, and tracked remote command processes are cancelled when access
is removed. Remote Hermes fails safe by stopping the container when a direct
command cannot be cancelled independently.
only through a confirmation-gated, audited action, then must run Test to
verify and pin the replacement before reuse.
locks keep concurrent tests, lifecycle actions, redeploys, restores, and
queue publication from racing a recreated host or stale runtime state.
provider mutation paths use the durable agent owner's current state. Failed
reconciliation stops or quarantines the runtime instead of reporting a false
success.
stay blocked, while cleanup-only paths can still remove workloads Nora owns.
Gemini extension manifest now publish against the exact release.
Maturity boundaries
Docker and Kubernetes remain the GA paths. Remote Docker, the OpenClaw-only
NemoClaw sandbox, and Proxmox are experimental. NemoClaw on Proxmox remains
blocked.
What feedback would help most
immediately in your environment?
use?
Release notes: https://github.com/solomon2773/nora/releases/tag/v1.16.4
Remote Docker guide:
https://noradocs.solomontsao.com/configuration/provisioner-backends/remote-docker
Quickstart: https://noradocs.solomontsao.com/quickstart
Walkthrough: https://nora.solomontsao.com/walkthrough.mp4
Disclosure: I maintain Nora. This announcement was drafted with AI assistance
and checked against the published release and current production metadata.
All reactions