WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

WARNING: The directory '/github/home/.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.

WARNING: Running pip as the 'root' user can result in broken permissions and conflicting behaviour with the system package manager. It is recommended to use a virtual environment instead: https://pip.pypa.io/warnings/venv

WARNING: The directory '/github/home/.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.

Docker pull failed with exit code 1

Docker pull failed with exit code 1

Docker pull failed with exit code 1

Docker pull failed with exit code 1

Docker pull failed with exit code 1

Docker pull failed with exit code 1

Docker pull failed with exit code 1

Docker pull failed with exit code 1

Docker pull failed with exit code 1

Docker pull failed with exit code 1

Docker pull failed with exit code 1

Process completed with exit code 1.

Process completed with exit code 1.

This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0

Docker pull failed with exit code 1, back off 2.1 seconds before retry.

Docker pull failed with exit code 1, back off 1.247 seconds before retry.

This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0

Docker pull failed with exit code 1, back off 6.535 seconds before retry.

Docker pull failed with exit code 1, back off 2.172 seconds before retry.

This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0

Docker pull failed with exit code 1, back off 4.672 seconds before retry.

Docker pull failed with exit code 1, back off 4.001 seconds before retry.

This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0

Docker pull failed with exit code 1, back off 3.261 seconds before retry.

Docker pull failed with exit code 1, back off 4.739 seconds before retry.

This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0

Docker pull failed with exit code 1, back off 5.143 seconds before retry.

Docker pull failed with exit code 1, back off 7.004 seconds before retry.

This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0

Docker pull failed with exit code 1, back off 7.974 seconds before retry.

Docker pull failed with exit code 1, back off 6.126 seconds before retry.

This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0

Docker pull failed with exit code 1, back off 5.093 seconds before retry.

Docker pull failed with exit code 1, back off 9.553 seconds before retry.

This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0

Docker pull failed with exit code 1, back off 8.806 seconds before retry.

Docker pull failed with exit code 1, back off 7.518 seconds before retry.

This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0

Docker pull failed with exit code 1, back off 2.187 seconds before retry.

Docker pull failed with exit code 1, back off 1.04 seconds before retry.

This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0

Docker pull failed with exit code 1, back off 5.363 seconds before retry.

Docker pull failed with exit code 1, back off 2.705 seconds before retry.

This job failure may be caused by using an out of date self-hosted runner. You are currently using runner version 2.320.0. Please update to the latest version 2.321.0

Docker pull failed with exit code 1, back off 3.83 seconds before retry.