...
 ./install.sh: line 40: cd: ../bindings/python: No such file or directory
  WARNING: The directory '/home/docker/.cache/pip' or its parent directory is not owned or is not writable by the current user. The cache has been disabled. Check the permissions and owner of that directory. If executing pip with sudo, you should use sudo's -H flag.
  ERROR: Directory '.' is not installable. Neither 'setup.py' nor 'pyproject.toml' found.
  Traceback (most recent call last):
    File "<string>", line 2, in <module>
    File "<pip-setuptools-caller>", line 34, in <module>
    File "/tmp/pip-install-6qvvduhj/xrootd_2f5bca47c43d46b9bed7a1e7d7727459/setup.py", line 205, in <module>
      setup(
    File "/home/docker/.pyenv/versions/issue-1474/lib/python3.10/site-packages/setuptools/__init__.py", line 108, in setup
      return distutils.core.setup(**attrs)
    File "/home/docker/.pyenv/versions/issue-1474/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 185, in setup
      return run_commands(dist)
    File "/home/docker/.pyenv/versions/issue-1474/lib/python3.10/site-packages/setuptools/_distutils/core.py", line 201, in run_commands
      dist.run_commands()
    File "/home/docker/.pyenv/versions/issue-1474/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 969, in run_commands
      self.run_command(cmd)
    File "/home/docker/.pyenv/versions/issue-1474/lib/python3.10/site-packages/setuptools/dist.py", line 1213, in run_command
      super().run_command(command)
    File "/home/docker/.pyenv/versions/issue-1474/lib/python3.10/site-packages/setuptools/_distutils/dist.py", line 988, in run_command
      cmd_obj.run()
    File "/tmp/pip-install-6qvvduhj/xrootd_2f5bca47c43d46b9bed7a1e7d7727459/setup.py", line 182, in run
      raise Exception( 'Install step failed!' )
  Exception: Install step failed!
  error: subprocess-exited-with-error
  
  × Running setup.py install for xrootd did not run successfully.
  │ exit code: 1
  ╰─> See above for output.
  
  note: This error originates from a subprocess, and is likely not a problem with pip.
  full command: /home/docker/.pyenv/versions/issue-1474/bin/python -u -c '
  exec(compile('"'"''"'"''"'"'
  # This is <pip-setuptools-caller> -- a caller that pip uses to run setup.py
  #
  # - It imports setuptools before invoking setup.py, to enable projects that directly
  #   import from `distutils.core` to work with newer packaging standards.
  # - It provides a clear error message when setuptools is not installed.
  # - It sets `sys.argv[0]` to the underlying `setup.py`, when invoking `setup.py` so
  #   setuptools doesn'"'"'t think the script is `-c`. This avoids the following warning:
  #     manifest_maker: standard file '"'"'-c'"'"' not found".
  # - It generates a shim setup.py, for handling setup.cfg-only projects.
  import os, sys, tokenize
  
  try:
      import setuptools
  except ImportError as error:
      print(
          "ERROR: Can not execute `setup.py` since setuptools is not available in "
          "the build environment.",
          file=sys.stderr,
      )
      sys.exit(1)
  
  __file__ = %r
  sys.argv[0] = __file__
  
  if os.path.exists(__file__):
      filename = __file__
      with tokenize.open(__file__) as f:
          setup_py_code = f.read()
  else:
      filename = "<auto-generated setuptools caller>"
      setup_py_code = "from setuptools import setup; setup()"
  
  exec(compile(setup_py_code, filename, "exec"))
  '"'"''"'"''"'"' % ('"'"'/tmp/pip-install-6qvvduhj/xrootd_2f5bca47c43d46b9bed7a1e7d7727459/setup.py'"'"',), "<pip-setuptools-caller>", "exec"))' install --record /tmp/pip-record-hq84ulx4/install-record.txt --single-version-externally-managed --compile --install-headers /home/docker/.pyenv/versions/issue-1474/include/site/python3.10/xrootd
  cwd: /tmp/pip-install-6qvvduhj/xrootd_2f5bca47c43d46b9bed7a1e7d7727459/
  Running setup.py install for xrootd ... error
error: legacy-install-failure

× Encountered error while trying to install package.
╰─> xrootd

note: This is an issue with the package mentioned above, not pip.
hint: See above for output from the failure.
(issue-1474) root@4a47d67a252c:~/data#