🤔[question] dialing to http://172.22.0.1:32862: dial tcp 172.22.0.1:32862: connect: connection refused

[mr-nealon]

Describe your question

[2024-03-05 07:09:00] releasing resources f7503e31-2f43-42a1-993b-046ee5ac1ed5 job-id="4e17705d-2829-4002-adbd-4885f4332b47" task-id="a5ce18c1-a859-4cbd-956e-dacbc3fea177" task-type="COMMAND"
[2024-03-05 07:09:00] incrementally released resources f7503e31-2f43-42a1-993b-046ee5ac1ed5 for a5ce18c1-a859-4cbd-956e-dacbc3fea177.1 component="resource-pool" name="default"
[2024-03-05 07:09:00] Command (generally-intense-basilisk) was terminated: allocation stopped early after all resources exited: resources exited successfully with a zero exit code job-id="4e17705d-2829-4002-adbd-4885f4332b47" task-id="a5ce18c1-a859-4cbd-956e-dacbc3fea177" task-type="COMMAND"
[2024-03-05 07:09:00] all resources are released for a5ce18c1-a859-4cbd-956e-dacbc3fea177.1 component="resource-pool" name="default"
[2024-03-05 07:09:00] allocation cleaned up and removed from cache component="allocation-service"
[2024-03-05 07:11:24] code=502, message=error dialing to http://172.22.0.1:32862: dial tcp 172.22.0.1:32862: connect: connection refused

Checklist

• Did you search the docs for a solution?
• Did you search github issues to find if somebody asked this question before?

[mr-nealon]

I configured a shared directory in NFS, but the cluster log keeps showing agent errors.

[ioga]

when you start a shell and try to connect to it, master tries to proxy your connection to the container. in this case the container address seems to end up being http://172.22.0.1:32862/.
do you have any idea why the master has issues connecting to it? for example, does that look like a correct IP address for the agent? or is there anything special about the networking, firewalls, proxies, and so on?