GitHub user dosubot[bot] added a comment to the discussion: docker installation from github fails
<!-- Answer --> Your setuptools timeout is almost certainly a network/proxy issue inside the container. Even if you set HTTP_PROXY and HTTPS_PROXY in `docker/.env`, they must be present in the container environment at runtime, and sometimes tools inside the container require both uppercase and lowercase variants. Here’s what to try next: 1. In your `docker/.env`, set all of these (replace with your actual proxy): ``` HTTP_PROXY=http://proxy-c04.xxx.local:3128 HTTPS_PROXY=http://proxy-c04.xxx.local:3128 http_proxy=http://proxy-c04.xxx.local:3128 https_proxy=http://proxy-c04.xxx.local:3128 NO_PROXY=localhost,127.0.0.1,db,redis no_proxy=localhost,127.0.0.1,db,redis ``` (Note the `http://` prefix is often required.) 2. Make sure you’re not mounting a local `docker/` directory in your compose file, as this can cause script/image mismatches and break builds. 3. If you’re running Docker with `--iptables=false`, this can break container networking and block outbound access to PyPI, even if proxy variables are set. If possible, try to resolve the nftables/iptables conflict and run Docker with iptables enabled again. Disabling iptables is known to cause connectivity issues for containers that need to reach the internet [source](https://github.com/apache/superset/discussions/34439). 4. To debug, start a shell in the failing container (e.g., `docker run -it --env-file docker/.env apachesuperset.docker.scarf.sh/apache/superset:latest-dev /bin/bash`), then run: ``` env | grep -i proxy curl -v https://pypi.org/simple/setuptools/ ``` This will show if the proxy variables are present and if you can reach PyPI from inside the container. If you still can’t reach PyPI, you may need to pre-download the required wheels and mount them into the container, or set up a local PyPI mirror as a workaround [source](https://github.com/apache/superset/discussions/34439). Let me know what you find when you check the environment and network from inside the container! <!-- Dosu Comment Footer --> *To reply, just mention [@dosu](https://go.dosu.dev/dosubot).* --- <sup>How did I do? [Good](https://app.dosu.dev/response-feedback/c8a5b4cd-2656-4c4f-84c7-fb20b6005991?feedback_type=great_response) | [Irrelevant](https://app.dosu.dev/response-feedback/c8a5b4cd-2656-4c4f-84c7-fb20b6005991?feedback_type=irrelevant_answer) | [Incorrect](https://app.dosu.dev/response-feedback/c8a5b4cd-2656-4c4f-84c7-fb20b6005991?feedback_type=incorrect_sources) | [Verbose](https://app.dosu.dev/response-feedback/c8a5b4cd-2656-4c4f-84c7-fb20b6005991?feedback_type=too_verbose) | [Hallucination](https://app.dosu.dev/response-feedback/c8a5b4cd-2656-4c4f-84c7-fb20b6005991?feedback_type=hallucination) | [Report 🐛](https://app.dosu.dev/response-feedback/c8a5b4cd-2656-4c4f-84c7-fb20b6005991?feedback_type=bug_report) | [Other](https://app.dosu.dev/response-feedback/c8a5b4cd-2656-4c4f-84c7-fb20b6005991?feedback_type=other)</sup> [](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=Your%20setuptools%20timeout%20is%20almost%20certainly%20a%20network/proxy%20issue%20inside%20the%20container.%20Even%20if%20you%20set%20HTTP_PROXY%20and%20HTTPS_PROXY%20in%20%60docker/.env%60%2C%20they%20must%20be%20present%20in%20the%20container%20environment%20at%20runtime%2C%20and%20sometimes%20tools%20inside%20the%20container%20require%20both%20uppercase%20and%20lowercase%20variants.%20%0A%0AHere%E2%80%99s%20what%20to%20try%20next%3A%0A%0A1.%20In%20your%20%60docker/.env%60%2C%20set%20all%20of%20these%20%28replace%20with%20your%20actual%20proxy%29%3A%0A%20%20%20%60%60%60%0A%20%20%20HTTP_PROXY%3Dhttp%3A//proxy-c04.xxx.local%3A3128%0A%20%20%20HTTPS_PROXY%3Dhttp%3A//proxy-c04.xxx.local%3A3128%0A%20%20%20http_proxy%3Dhttp%3A//proxy-c04.xxx.local%3A3128 %0A%20%20%20https_proxy%3Dhttp%3A//proxy-c04.xxx.local%3A3128%0A%20%20%20NO_PROXY%3Dlocalhost%2C127.0.0.1%2Cdb%2Credis%0A%20%20%20no_proxy%3Dlocalhost%2C127.0.0.1%2Cdb%2Credis%0A%20%20%20%60%60%60%0A%20%20%20%28Note%20the%20%60http%3A//%60%20prefix%20is%20often%20required.%29%0A%0A2.%20Make%20sure%20you%E2%80%99re%20not%20mounting%20a%20local%20%60docker/%60%20directory%20in%20your%20compose%20file%2C%20as%20this%20can%20cause%20script/image%20mismatches%20and%20break%20builds.%0A%0A3.%20If%20you%E2%80%99re%20running%20Docker%20with%20%60--iptables%3Dfalse%60%2C%20this%20can%20break%20container%20networking%20and%20block%20outbound%20access%20to%20PyPI%2C%20even%20if%20proxy%20variables%20are%20set.%20If%20possible%2C%20try%20to%20resolve%20the%20nftables/iptables%20conflict%20and%20run%20Docker%20with%20iptables%20enabled%20again.%20Disabling%20iptables%20is%20known%20to%20cause%20connectivity%20issues%20for%20containers%20that%20need%20to%20reach%20the%20internet%20%5Bsource%5D%28 https%3A//github.com/apache/superset/discussions/34439%29.%0A%0A4.%20To%20debug%2C%20start%20a%20shell%20in%20the%20failing%20container%20%28e.g.%2C%20%60docker%20run%20-it%20--env-file%20docker/.env%20apachesuperset.docker.scarf.sh/apache/superset%3Alatest-dev%20/bin/bash%60%29%2C%20then%20run%3A%0A%20%20%20%60%60%60%0A%20%20%20env%20%7C%20grep%20-i%20proxy%0A%20%20%20curl%20-v%20https%3A//pypi.org/simple/setuptools/%0A%20%20%20%60%60%60%0A%20%20%20This%20will%20show%20if%20the%20proxy%20variables%20are%20present%20and%20if%20you%20can%20reach%20PyPI%20from%20inside%20the%20container.%0A%0AIf%20you%20still%20can%E2%80%99t%20reach%20PyPI%2C%20you%20may%20need%20to%20pre-download%20the%20required%20wheels%20and%20mount%20them%20into%20the%20container%2C%20or%20set%20up%20a%20local%20PyPI%20mirror%20as%20a%20workaround%20%5Bsource%5D%28https%3A//github.com/apache/superset/discussions/34439%29.%0A%0ALet%20me%20know%20what%20you%20find%20when%20you%20check%20the%20environment%20and%20ne twork%20from%20inside%20the%20container%21) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/37610) GitHub link: https://github.com/apache/superset/discussions/37610#discussioncomment-15691334 ---- This is an automatically sent email for [email protected]. To unsubscribe, please send an email to: [email protected] --------------------------------------------------------------------- To unsubscribe, e-mail: [email protected] For additional commands, e-mail: [email protected]
