when pants starts up, it will use the pids directory to locate the pid and port of a running pantsd, and attempt to connect to it on

localhost:${instance_specific_port}

. if you launch a container atop an existing workspace, and networking is configured the right way, it might attempt to connect to an instance of the daemon outside of the container…?