How to fix missing pip on minimal Ubuntu CI agents without sudo or apt

Developers running self-hosted CI/CD agents on minimal Ubuntu images often encounter 'No module named pip' errors that have nothing to do with network connectivity. Debian and Ubuntu deliberately strip pip and ensurepip from the base python3 package, requiring separate apt packages that are unavailable on no-sudo, minimal CI environments. Attempts to work around the issue using ensurepip or Python virtual environments fail for the same underlying reason, since venv's pip-bootstrapping also depends on the missing ensurepip module. The reliable fix is to use get-pip.py, a self-contained bootstrapper maintained by the Python Packaging Authority that installs pip directly without relying on ensurepip, apt, or root access. Before applying any fix, developers should first verify the agent has outbound network access to PyPI, as firewall or egress issues can produce similar symptoms.