Splunk Enterprise

docker deployment client not connecting to docker deployment server

Zasn00t
Observer

Hi guys, 

Currently building my own lab in docker where each instance is mapped to a different host port using -P with docker run

Whenever I attempt to set anything in < targetUri => within my Deployment Client , the DC never ever phones home.

Variations of my DC.conf:

Deployment server Container name solely:

 

 

 

[deployment-client]
phoneHomeIntervalInSecs = 60
disabled = false


[target-broker:deploymentServer]
targetUri = DeploymentServer 

 

 

 

 

Deployment server ContaierName w/mgmt port: 

 

 

 

[deployment-client]
phoneHomeIntervalInSecs = 60
disabled = false


[target-broker:deploymentServer]
targetUri = DeploymentServer:8089

 

 

Deployment Server Container IP w/mgmt port

 

 

 

 

[deployment-client]
phoneHomeIntervalInSecs = 60
disabled = false


[target-broker:deploymentServer]
targetUri = 172.19.0.2:8089

 

 

 


IP grabbed with

 

 

 

docker inspect -f '{{range.NetworkSettings.Networks}}{{.IPAddress}}{{end}}' DeploymentServer

 

 

 

  • Other info: 
    • I have an app in deployment-apps on my DS
    • Internal logs from my indexer is as follows from my UF1 when initiating with IP and port
    • I can ping the IPs when on each machine 
    • I turned off windows firewall to ensure it wasn't being blocked, nothing changed
    • Even when setting the DS within -e on the UF container it does not work

Internal logs from uf01:

- Phonehome thread started

channel=tenantService/handshake Will retry sending handshake message to DS; err=not_connected

channel=tenantService/handshake Will retry sending handshake message to DS; err=not_connected

- Handshake done

 

docker ps output: 

IDX1

4c5998526d1b splunk/splunk:latest "/sbin/entrypoint.sh…" 3 hours ago Up About an hour (healthy) 0.0.0.0:49169->8000/tcp, :::49169->8000/tcp, 0.0.0.0:49168->8065/tcp, :::49168->8065/tcp, 0.0.0.0:49167->8088/tcp, :::49167->8088/tcp, 0.0.0.0:49166->8089/tcp, :::49166->8089/tcp, 0.0.0.0:49165->8191/tcp, :::49165->8191/tcp, 0.0.0.0:49164->9887/tcp, :::49164->9887/tcp, 0.0.0.0:49163->9997/tcp, :::49163->9997/tcp idx1

DS
843454a553ec splunk/splunk:latest "/sbin/entrypoint.sh…" 3 hours ago Up About an hour (healthy) 0.0.0.0:49159->8000/tcp, :::49159->8000/tcp, 0.0.0.0:49158->8065/tcp, :::49158->8065/tcp, 0.0.0.0:49157->8088/tcp, :::49157->8088/tcp, 0.0.0.0:49156->8089/tcp, :::49156->8089/tcp, 0.0.0.0:49155->8191/tcp, :::49155->8191/tcp, 0.0.0.0:49154->9887/tcp, :::49154->9887/tcp, 0.0.0.0:49153->9997/tcp, :::49153->9997/tcp DeploymentServer

UF01
923c0bc20fb3 splunk/universalforwarder:latest "/sbin/entrypoint.sh…" 3 hours ago Up About an hour (healthy) 0.0.0.0:49162->8088/tcp, :::49162->8088/tcp, 0.0.0.0:49161->8089/tcp, :::49161->8089/tcp, 0.0.0.0:49160->9997/tcp, :::49160->9997/tcp

its definitely confusing. Anyone able to help me out? 

Labels (2)
0 Karma

Zasn00t
Observer

Also:

When checking for listed deployment clients on the DS it simply says:

Deployment Client is disabled

Tags (1)
0 Karma
Get Updates on the Splunk Community!

Index This | What is broken 80% of the time by February?

December 2025 Edition   Hayyy Splunk Education Enthusiasts and the Eternally Curious!    We’re back with this ...

Unlock Faster Time-to-Value on Edge and Ingest Processor with New SPL2 Pipeline ...

Hello Splunk Community,   We're thrilled to share an exciting update that will help you manage your data more ...

Splunk MCP & Agentic AI: Machine Data Without Limits

Discover how the Splunk Model Context Protocol (MCP) Server can revolutionize the way your organization uses ...