Your pollers, in containers. Beta
Deploy a Centreon poller as Docker containers: the central generates a single command, the poller starts and connects by itself. Available as a beta with Centreon 26.10.
One generated command
The central builds the install command with the poller identity and token: copy, paste, done.
Outbound connection only
The poller connects to the central (HTTPS + 5669): no inbound port to open towards your remote sites.
Docker Compose stack
Engine and Gorgone in separate containers on Debian 13, plus optional SNMP traps, VMware and agent support.
- 1
Prepare the central once
Enable Gorgone pullwss and the Apache reverse proxy on the central, so container pollers can connect. Central prerequisites →
- 2
Generate the command
In the central: pollers menu, then Create new poller. Choose the Container environment, select a poller-type token, then Generate installation command.
- 3
Run it on the Docker host
With a user allowed to run containers. The script checks Docker, writes .env and docker-compose.yaml, then starts the stack:
curl -fsSL <CENTRAL_URL>/poller/install.sh | bash -s -- \ --type docker \ --poller_token <TOKEN_NAME>:<TOKEN_SECRET> \ --uid <POLLER_UID> --name '<POLLER_NAME>' \ --central_url <CENTRAL_URL> \ --appsecret <APP_SECRET> --salt <SALT>Template only: use the command generated by your central, it contains your poller identifiers.
Check and export
docker compose ps: oncegorgoneis healthy, go back to the central and click Export configuration. The poller appears as running in Configuration › Pollers.
Install options
--with-snmptrap- Receive SNMP traps (snmptrapd + centreontrapd, UDP 162).
--with-vmware- Add the VMware connector (image to build locally, SDK not redistributable).
--with-cma- Receive data from Centreon Monitoring Agents (OpenTelemetry gRPC, port 4317).
--tz <timezone>- Poller time zone (UTC by default).
--no-start- Generate the files without starting the stack.
Prerequisites
- A Centreon 26.10 platform.
- A Linux host with Docker Engine and Docker Compose v2.
- Outbound access to the central: web port (443/80) and TCP 5669.
- A poller-type authentication token created on the central.
The central server in containers is next
We are now working on containerizing the central server too. Stay tuned: it will be announced here and in the release notes.