Invalid Pypi setting in multiple docker images

[LC-John]

Hi, there. I am working on a project to evaluate agents inside docker containers. In other word, I need to install various agents inside the released docker images. However, I noticed that there are plenty of docker images have Pypi issues, where http connection is set to localhost. After diving into the dockerfiles, I find the following lines.

pypi-timemachine 2024-06-07 --port 9876 &
pip config set global.index-url http://127.0.0.1:9876/

From my understanding, this connects to your internal Pypi platform. My question is that if I can set global.index-url back to the official one (https://pypi.org/simple) without harming the following evaluation procedures.

Also, another issue is that the released docker images are not from a unified base docker. Therefore, I doubt there are more issues (e.g., network connection) like this Pypi one. Is it possible for you to provide the rules, following which the dockerfiles are generated? Currently, I have faced so many conner cases, and I have to fix them one docker image by another... With a documentation, maybe I can speed up and fix them quickly.

[jeff-da]

Hey @LC-John , highly suggest to use the Docker images from DockerHub and not try to build the images. Let me know if there's a reason why you can't do so

[LC-John]

Thanks for your reply! Yeah, I am using images from DockerHub. The problem is that I need to install some necesary python packages inside the docker container, so that my agent under evaluation can execute.

For some images, pip config set global.index-url http://127.0.0.1:9876/ blocks the connection to pypi, and therefore I cannot install anything. My current solution is reseting global.index-url back to https://pypi.org/simple, and then install those packages I need.

The concern of mine is that I do not know if my current solution would potentially harm the environment, as the released images are way too compliated... (and there may be many corner cases...)