Joe LeVeque 6333bb73b0 Explicitly call pip2 rather than pip in locations where both pip2 and pip3 are installed (#5747) ... As part of the transition from Python 2 to Python 3, we are installing both pip2 and pip3 in the slave and config-engine containers. This PR replaces calls to `pip` in these containers with an explicit call to `pip2` to ensure the proper version of pip is executed, no matter which version of pip is aliased to `pip`, as we no longer rely on that alias. Also some other pip-related cleanup		2020-10-30 09:43:14 -07:00
..
base_image_files	[submodule update] Add SSD Health tools (#3218)	2019-10-04 10:52:58 -07:00
ssd_tools	[submodule update] Add SSD Health tools (#3218)	2019-10-04 10:52:58 -07:00
critical_processes	[dockers] Update critical_processes file syntax (#4831)	2020-06-25 21:18:21 -07:00
docker_init.sh	[docker-pmon] Fix copy of fancontrol config file (#5037)	2020-07-28 00:23:21 -07:00
docker-pmon.supervisord.conf.j2	[dockers][supervisor] Increase event buffer size for dependent-startup (#5247)	2020-09-08 23:36:38 -07:00
Dockerfile.j2	Explicitly call pip2 rather than pip in locations where both pip2 and pip3 are installed (#5747)	2020-10-30 09:43:14 -07:00
lm-sensors.sh	[sensors]: Workaround for apparent bug in lm-sensors (#1058)	2017-10-20 11:01:26 -07:00
start.sh	Explicitly call pip2 rather than pip in locations where both pip2 and pip3 are installed (#5747)	2020-10-30 09:43:14 -07:00