docker method to run pulse-docker-agent

[scelfo]

Is your feature request related to a problem? Please describe.
I would like to add my TrueNAS server(s) as docker hosts in Pulse. TrueNAS does not allow installation of custom packages, but TrueNAS can run docker containers.

Describe the solution you'd like
I'd like to see a method of installing pulse-docker-agent that is based on docker, specifically docker compose. The docker container would need to be given access to /var/run/docker.sock and then docker itself can ensure that pulse-docker-agent is running. This wouldn't be preferred over the current way to install a systemd unit to ensure the agent runs at startup but it would be a nice compromise for docker hosts where the main OS can not be modified.

This would require either a separate pulse-docker-agent published docker package or perhaps the agent could be bundled into the existing rcourtman/pulse with a compose.yaml that overrides the default startup to run the agent instead of Pulse.

Describe alternatives you've considered
None really. There are ways to modify TrueNAS but I would prefer to keep it unmodified.

Additional context
None.

[darthrater78]

Maybe I'm misunderstanding,but there's a docker version of the agent you can run now.

[scelfo]

🤦 You’re right, there is. My mistake!! I guess the feature request is to make this more obvious in the documentation.

…

On Sat, Oct 25, 2025 at 5:18 AM darthrater78 ***@***.***> wrote: *darthrater78* left a comment (rcourtman/Pulse#603) <#603 (comment)> Maybe I'm misunderstanding,but there's a docker version of the agent you bcd27664-4a9b-4efe-8515-213b6da559d0_562x270.webp (view on web) <https://github.com/user-attachments/assets/cb5f0011-e190-46f0-980a-8ae72278e078> can run now. — Reply to this email directly, view it on GitHub <#603 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA7OR3L6V6NS5NCJJ24RMT3ZNL7TAVCNFSM6AAAAACKBQFSXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINBWGU3DMNZQHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[darthrater78]

Honestly, that's a good point. I actually stumbled upon this when I was looking into the agent install.

It should definitely be called out stronger in the documentation.

[stubbo66]

Funnily enough I was just installing this, it is in the documentation if you follow the links to the agent installation.

However, having installed it, all I get is a 400 Bad Request in the logs.

[darthrater78]

For the docker install? I just did a write up if it helps

https://ramblingnonsense.nscriven.net/p/checking-the-pulse

[stubbo66]

My docker compose is the same as yours, but I get this in the container logs

2025-10-25T15:35:07Z INF Starting Pulse Docker agent | pulse_url=https://pulse.******.** interval=30000
2025-10-25T15:35:07Z DBG Checking for agent updates | component=pulse-docker-agent
2025-10-25T15:35:07Z DBG Agent is up to date | component=pulse-docker-agent version=v4.22.0-rc.6
2025-10-25T15:35:07Z ERR Failed to send initial report | component=pulse-docker-agent error=target https://pulse.******.**: pulse responded with status 400 Bad Request
2025-10-25T15:35:37Z ERR Failed to send docker report | component=pulse-docker-agent error=target https://pulse.******.**: pulse responded with status 400 Bad Request
2025-10-25T15:36:07Z ERR Failed to send docker report | component=pulse-docker-agent error=target https://pulse.******.**: pulse responded with status 400 Bad Request
2025-10-25T15:36:37Z ERR Failed to send docker report | component=pulse-docker-agent error=target https://pulse.******.**: pulse responded with status 400 Bad Request
2025-10-25T15:37:07Z ERR Failed to send docker report | component=pulse-docker-agent error=target https://pulse.******.**: pulse responded with status 400 Bad Request

I am running behind traefik, but I have tried it direct as well and not using https with the exact same result. If I ran the agent natively in the LXC it works, although oddly I only ever get one docker instance shown and it cycles through all the reporters....I think it might be because I used a cloned instance I have with docker and everything set up how I like it so every VM must have the same docker host ID.

[scelfo]

Thanks that write up covers exactly what I need. And to your point my home is an enterprise with users who expect uptime and just like you, that’s why I’m using Pulse. With the docker container agent I’m also going to put one on my home assistant green so have that monitored.

…

On Sat, Oct 25, 2025 at 9:31 AM darthrater78 ***@***.***> wrote: *darthrater78* left a comment (rcourtman/Pulse#603) <#603 (comment)> For the docker install? I just did a write up if it helps https://ramblingnonsense.nscriven.net/p/checking-the-pulse — Reply to this email directly, view it on GitHub <#603 (comment)>, or unsubscribe <https://github.com/notifications/unsubscribe-auth/AAA7OR2RSOAX7QTXLV5SBHD3ZOJVLAVCNFSM6AAAAACKBQFSXCVHI2DSMVQWIX3LMV43OSLTON2WKQ3PNVWWK3TUHMZTINBWHAZTSMRQHE> . You are receiving this because you authored the thread.Message ID: ***@***.***>

[stubbo66]

Just following up on my host not found errors.....I moved my docker config into an include file because it's going to be used in a lot of docker LXCs, rebuilt, and it started working. I'll be honest, I haven't go the first clue what changed...but it's working now.

I also had to manually set the PULSE_AGENT environment variable on every docker instance as I had cloned from a single setup of docker for all of my LXCs so must all have the same engine ID.

[darthrater78]

It's not the destination, it's the journey that's fun. :p

[adirburke]

Just following up on my host not found errors.....I moved my docker config into an include file because it's going to be used in a lot of docker LXCs, rebuilt, and it started working. I'll be honest, I haven't go the first clue what changed...but it's working now.

I also had to manually set the PULSE_AGENT environment variable on every docker instance as I had cloned from a single setup of docker for all of my LXCs so must all have the same engine ID.

I am having the same issue. Just getting 400's back from the server. Any idea how you fixed it ?

services:
  pulse-agent:
    image: ghcr.io/rcourtman/pulse-docker-agent:latest
    container_name: pulse-agent
    restart: unless-stopped
    environment:
      - PULSE_TOKEN=61xxxx
      - PULSE_URL=http://10.10.0.33:7655
    volumes:
      - /var/run/docker.sock:/var/run/docker.sock```

`Attaching to pulse-agent
pulse-agent  | {"level":"info","pulse_url":"http://10.10.0.33:7655","interval":30000,"time":"2025-10-27T00:17:30Z","message":"Starting Pulse Docker agent"}
pulse-agent  | {"level":"debug","component":"pulse-docker-agent","time":"2025-10-27T00:17:30Z","message":"Checking for agent updates"}
pulse-agent  | {"level":"debug","component":"pulse-docker-agent","version":"v4.22.0-rc.6","time":"2025-10-27T00:17:30Z","message":"Agent is up to date"}
pulse-agent  | {"level":"info","pulse_url":"http://10.10.0.33:7655","interval":30000,"time":"2025-10-27T00:17:30Z","message":"Starting Pulse Docker agent"}
pulse-agent  | {"level":"debug","component":"pulse-docker-agent","time":"2025-10-27T00:17:30Z","message":"Checking for agent updates"}
pulse-agent  | {"level":"debug","component":"pulse-docker-agent","version":"v4.22.0-rc.6","time":"2025-10-27T00:17:30Z","message":"Agent is up to date"}
pulse-agent  | {"level":"error","component":"pulse-docker-agent","error":"target http://10.10.0.33:7655: pulse responded with status 400 Bad Request","time":"2025-10-27T00:17:30Z","message":"Failed to send initial report"}
pulse-agent  | {"level":"error","component":"pulse-docker-agent","error":"target http://10.10.0.33:7655: pulse responded with status 400 Bad Request","time":"2025-10-27T00:17:30Z","message":"Failed to send initial report"}`

[adirburke]

I worked it out, All my docker machine ids were the same. As i cloned them all. Might be worth putting a comment in the docs about that as alot of people will clone off a main base and even thought they have different host machine ids the docker ids were the same