# Docker Space Receives Seemingly Random TERM **URL:** \ **Category:** Spaces\ **Created:** [December 30, 2024, 3:19am UTC](https://discuss.huggingface.co/t/docker-space-receives-seemingly-random-term/133530 "2024-12-30T03:19:49Z")\ **Posts on this page:** 1\ **Showing post:** 3
**Author:** ![benjamin-paine](https://sea2.discourse-cdn.com/hellohellohello/user_avatar/discuss.huggingface.co/benjamin-paine/32/38306_2.png) [@benjamin-paine](https://discuss.huggingface.co/u/benjamin-paine)\ **Post date:** [December 30, 2024, 2:19pm UTC](https://discuss.huggingface.co/t/docker-space-receives-seemingly-random-term/133530/3 "2024-12-30T14:19:36Z")
Hey @John6666! I hoped you might show up in this thread 🙂 For a bit more information, I did encounter the “permanently building” issue multiple time, which I found information about in this thread (also featuring you: [Space is Building... permanently](https://discuss.huggingface.co/t/space-is-building-permanently/99740)). If I make a barebones proof of concept app featuring nginx, supervisord and uvicorn, **it refuses to build.** This example space I made public: [Nginx Supervisord - a Hugging Face Space by benjamin-paine](https://huggingface.co/spaces/benjamin-paine/nginx-supervisord). To be clear, while this seems related to the initial issue, it may not be. If using nginx as a proxy for internal connections is disallowed, I suppose I could understand, but HF themselves recommend using it in their documentation (I can’t add any more links - it’s at huggingface DOT co/docs/hub/en/spaces-sdks-docker) and it’s one of the easier tools to set up for adapting apps that run on multiple ports to a single-port space. It’d be a huge shame if we’re forced into using some esoteric-but-unflagged python package for proxying (or even worse, rolling our own) because of collateral damage from fighting bad actors. --- _[View the full topic](https://discuss.huggingface.co/t/docker-space-receives-seemingly-random-term/133530)._