Skip to content

HostManager: Improve handling of docker containers #463

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
BrianJKoopman merged 11 commits into from
Apr 2, 2026
Merged

HostManager: Improve handling of docker containers #463

Show file tree
Hide file tree
Changes from all commits
Commits
Show all changes
11 commits
Select commit Hold shift + click to select a range
073d1a4
Refactor HostManager to use dataclasses
mhasself Mar 27, 2026
ac10abd
HostManager: collect more data about docker images
mhasself Mar 27, 2026
0a5d353
HostManager: track orphan containers explicitly.
mhasself Mar 27, 2026
60798de
HostManager: remove_orphans task, to clean things up
mhasself Mar 27, 2026
e722f2a
HostManager: report agents that need a restart. docker_pull task
mhasself Mar 28, 2026
197a09d
HostManager: make docker non-agent handling "passive"
mhasself Mar 29, 2026
08f4d68
HostManager: ability to exit without taking down all running docker s…
mhasself Mar 29, 2026
97a58be
HostManager: wait 11 seconds, instead of 5, for exit
mhasself Mar 29, 2026
be91ddc
HostManager: update docs and minor bugfixes for recent changes
mhasself Mar 30, 2026
7e7c7dc
HostManager: is_running and exit_code props
mhasself Apr 1, 2026
b202c75
HostManager: fix how unmanaged dockers transition to managed
mhasself Apr 2, 2026
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
16 changes: 11 additions & 5 deletions docs/user/centralized_management.rst
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -192,8 +192,14 @@ with a [d] appended to their usual agent_class name.

If HostManager finds services in the docker-compose.yaml that don't
seem to correspond to agent instances in site config, it will still
permit them to be "managed" (brought up and down). The agent_class,
in ocsbow or ocs-web, will show up as simply "[docker]".
track their state and make it visible in ocsbow / ocs-web. The
agent_class will show up as simply "[docker]". HostManager can be
told to bring the containers up or down, but this state will not be
recorded as a persistent target state. Other than during the request
and transition stages, the target state will be recorded as "passive".
This means such services can be brought up and down by other means
(i.e. docker compose on the command line) without any conflict with
HostManager.


Advanced host config
Expand All @@ -212,8 +218,8 @@ It is possible to mix host- and docker-based agents in a single host
config block, and control them all with a single HostManager instance.
Just make sure your docker-based agents are marked with ``'manage':
'docker'`` in site config, and have service name ``ocs-[instance-id]``
as usual. Usually, docker-based agents have some command line
parameter overrides set in docker-compose.yaml (or in the site config
as usual. Sometimes docker-based agents will require some command line
parameter overrides in docker-compose.yaml (or in the site config
block), because the crossbar address is different or weird from inside
the container. If the hostname, in the docker container, is not the
same as on the host system then specify the native host hostname with
Expand Down Expand Up @@ -311,7 +317,7 @@ specific instance will show up with agent-class "?/[docker]" and an
instance-id corresponding to the service name. For example::

[instance-id] [agent-class] [state] [target]
influxdb ?/[docker] up up
influxdb ?/[docker] up passive


``state`` and ``target``
Expand Down
Loading