containers.network now needs a restart to apply #1969

Open
opened 2026-11-13 13:15:18 +00:00 by sam · 1 comment
Owner

Problem

Since #1867, [containers].network is the network the egress relay joins, and the relay starts once at boot. A change saved through the control plane (container runtime policies) is accepted but takes effect only after archied restarts. Before, the next task container picked it up.

Wanted

Either restart the relay on the new network when the setting changes (without dropping running tasks' connections), or mark the setting as needing a restart wherever it is edited.

Done when

Saving a new network either takes effect for the next task, or the dashboard says a restart is needed to apply it.

## Problem Since #1867, [containers].network is the network the egress relay joins, and the relay starts once at boot. A change saved through the control plane (container runtime policies) is accepted but takes effect only after archied restarts. Before, the next task container picked it up. ## Wanted Either restart the relay on the new network when the setting changes (without dropping running tasks' connections), or mark the setting as needing a restart wherever it is edited. ## Done when Saving a new network either takes effect for the next task, or the dashboard says a restart is needed to apply it.
sam added the buglow labels 2026-11-13 13:15:26 +00:00
Author
Owner

Left at low priority. A live change isn't safe: the network decides the host gateway that the embedded NATS and egress proxy listen on, and the relay is attached to running task networks. Proposed fix if picked up: report the boot-time network through apply-status, and have the dashboard show 'restart archied to apply' when the stored value differs. Only relevant on the Docker runtime; the field is hidden under OpenShell.

Left at low priority. A live change isn't safe: the network decides the host gateway that the embedded NATS and egress proxy listen on, and the relay is attached to running task networks. Proposed fix if picked up: report the boot-time network through apply-status, and have the dashboard show 'restart archied to apply' when the stored value differs. Only relevant on the Docker runtime; the field is hidden under OpenShell.
sam added the deferred label 2026-11-15 17:26:09 +00:00
Sign in to join this conversation.
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: sam/archie#1969