Storage Transfer Service Agent Not Connecting to Pool and No Logs

I am setting up Storage Transfer Service (STS) On-Premises Agents using Docker on my local machine (macOS). The agent container runs, but:

Problems

  • Agents appear to start but never connect to the Agent Pool.
    • In the STS console → Agent Pools → Agents, nothing shows up.
    • Status remains “0/0 agents connected”.
  • No logs are generated in the running containers, even though I mounted:
--mount type=bind,source=$HOME/sts-agent/logs,target=/var/log/sts

I checked:

  • Service account JSON exists and is mounted correctly.
  • Outbound directory is mounted.
  • The local directory paths exist.
  • Firewall should not block outbound HTTPS traffic (macOS local workstation).
"Id": "84df7b0233ccb30ac73918e01e12963cd4247d73e6235e905b5cec79d8ab071d",
	"Created": "2025-12-05T03:10:40.270241472Z",
	"Path": "/google3/cloud/transfer/online/onprem/autoupdate/autoupdate",
	"Args": [
		"--agent-pool=myfirstagentpool",
		"--hostname=MacBook-Pro-2.local",
		"--log-dir=/Users/(PII Removed by Staff)/Documents/udemy_gcp_engineer/sts/sts-log",
		"--project-id=aerobic-star-480209-q9",
		"--creds-file=/Users/(PII Removed by Staff)/Documents/udemy_gcp_engineer/sts-agent/creds/sts-sa.json"
	],
	"State": {
		"Status": "running",
		"Running": true,
		"Paused": false,
		"Restarting": false,
		"OOMKilled": false,
		"Dead": false,
		"Pid": 9780,
		"ExitCode": 0,
		"Error": "",
		"StartedAt": "2025-12-05T03:10:40.339354472Z",
		"FinishedAt": "0001-01-01T00:00:00Z"
	},

Local dirs exist;

~/sts-agent/logs
~/sts-agent/creds/sts-sa.json
~/sts-agent/outbound

I have checked reququired IAM roles as well.

Complete command as follows;

gcloud transfer agents install --pool=myfirstagentpool --count=1 --creds-file=/Users/adnandmth/Documents/udemy_gcp_engineer/sts-agent/creds/sts-sa.json --mount-directories=/Users/(PII Removed by Staff)/Documents/udemy_gcp_engineer/sts/outbound --logs-directory=/Users/(PII Removed by Staff)/Documents/udemy_gcp_engineer/sts/sts-log

and output as follows;
[1/3] Credentials found ✓
[2/3] Docker found ✓
WARNING: The requested image’s platform (linux/amd64) does not match the detected host platform (linux/arm64/v8) and no specific platform was requested
84df7b0233ccb30ac73918e01e12963cd4247d73e6235e905b5cec79d8ab071d
[3/3] Agent installation complete! ✓

To confirm your agents are connected, go to the following link in your browser,
and check that agent status is ‘Connected’ (it can take a moment for the status
to update and may require a page refresh):

If your agent does not appear in the pool, check its local logs by running
“docker container logs [container ID]”. The container ID is the string of random
characters printed by step [2/3]. The container ID can also be found by running
“docker container list [container ID]”.

1 Like

Hey,

Hope you’re keeping well.

It looks like the agent process is running but not registering with STS, and the lack of logs suggests it may not be starting correctly inside the container. The warning about platform mismatch is a key clue here — you’re on macOS with Apple Silicon (arm64), but the STS agent image is built for linux/amd64. You’ll need to explicitly pull/run the image with --platform=linux/amd64 so Docker will use emulation.

Thanks and regards,
Taz

Hi,

Thanks for your response!

Hi,

Thanks for your response!

Even after explicitly run the image with --platform=linux/amd64 , the agents are still not connecting.

I have tested the installation on MacOS using AMD64 platform and it worked perfectly fine. My conclusion is that the platform mismatch is causing the issue and explicitly emulate the AMD64 by adding --platform=linux/amd64 flag when running the container did not resolve it.