#17622 Running `./pants -no-pantsd --no-watch-filesystem version` under linux/amd64 docker image on ARM macOS requires ~4G of memory New issue created by huonw Describe the bug As discussed in https://pantsbuild.slack.com/archives/C046T6T9U/p1669150590877779, it seems pants doesn't easily run under docker with a ARM macOS host:

uname -ms 
# Darwin arm64

docker pull --platform linux/amd64 python@sha256:c1613835d7be322f98603f356b9e0c9d40f9589e94dc9f710e714a807a665700  # 3.9 at the time of writing
# ...

docker run -t --platform linux/amd64 python@sha256:c1613835d7be322f98603f356b9e0c9d40f9589e94dc9f710e714a807a665700 bash -c 'echo -e "[GLOBAL]\npants_version = \"2.14.0\"" > pants.toml && curl -L -O <https://static.pantsbuild.org/setup/pants> && chmod +x ./pants && ./pants -ldebug --no-pantsd --no-watch-filesystem  version'
# ...
# Bootstrapping Pants using /usr/local/bin/python3.9
# ...
# New virtual environment successfully created at /root/.cache/pants/setup/bootstrap-Linux-x86_64/2.14.0_py39.
# 22:53:01.00 [DEBUG] File handle limit is: 1048576
# 22:53:03.05 [DEBUG] Using [cache::CommandRunner { inner: bounded::CommandRunner { inner: nailgun::CommandRunner { inner: local::CommandRunner { .. }, .. }, .. }, .. }, cache::CommandRunner { inner: bounded::CommandRunner { inner: nailgun::CommandRunner { inner: local::CommandRunner { .. }, .. }, .. }, .. }] for process execution.
# 22:53:04.12 [DEBUG] Launching 1 roots (poll=false).
# 22:53:04.26 [DEBUG] computed 1 nodes in 0.136536 seconds. there are 7 total nodes.
# 22:53:04.51 [DEBUG] File handle limit is: 1048576
# 22:53:06.61 [DEBUG] Using [cache::CommandRunner { inner: bounded::CommandRunner { inner: nailgun::CommandRunner { inner: local::CommandRunner { .. }, .. }, .. }, .. }, cache::CommandRunner { inner: bounded::CommandRunner { inner: nailgun::CommandRunner { inner: local::CommandRunner { .. }, .. }, .. }, .. }] for process execution.
# 22:53:06.83 [DEBUG] specs are: Specs(includes=RawSpecs(description_of_origin='CLI arguments', address_literals=(), file_literals=(), file_globs=(), dir_literals=(), dir_globs=(), recursive_globs=(), ancestor_globs=(), unmatched_glob_behavior=<GlobMatchErrorBehavior.error: 'error'>, filter_by_global_options=True, from_change_detection=False), ignores=RawSpecs(description_of_origin='CLI arguments', address_literals=(), file_literals=(), file_globs=(), dir_literals=(), dir_globs=(), recursive_globs=(), ancestor_globs=(), unmatched_glob_behavior=<GlobMatchErrorBehavior.error: 'error'>, filter_by_global_options=False, from_change_detection=False))
# 22:53:06.83 [DEBUG] changed_options are: ChangedOptions(since=None, diffspec=None, dependees=<DependeesOption.NONE: 'none'>)
# 22:53:06.83 [DEBUG] Launching 1 roots (poll=false).
# 22:53:06.85 [WARN] Please either set `enabled = true` in the [anonymous-telemetry] section of pants.toml to enable sending anonymous stats to the Pants project to aid development, or set `enabled = false` to disable it. No telemetry sent for this run. An explicit setting will get rid of this message. See <https://www.pantsbuild.org/v2.14/docs/anonymous-telemetry> for details.
# 22:53:06.86 [DEBUG] computed 1 nodes in 0.024304 seconds. there are 12 total nodes.
# 2.14.0

The

--no-pantsd --no-watch-filesystem

are prompted by https://www.pantsbuild.org/docs/prerequisites#macos. Watching top (e.g.

docker ps

to find the running container name, followed by

docker exec -t ...name... top

) indicates that the memory usage of the pants python process is reasonable for a while, and then starts climbing to resident ~3.6G and virtual ~600G before succeeding. When running in a container with a lower memory limit (e.g. 3G), the server is killed instead (after the

File handle limit is: 1048576

log line that's at

22:53:04.51

in the quote above). Pants version 2.14.0 OS macOS Additional info N/A pantsbuild/pants