GitHub user dosubot[bot] added a comment to the discussion: docker installation
from github fails
<!-- Answer -->
The docker-proxy error isn't caused by Superset or its configuration—it's
almost always a host-level Docker networking issue. Even if `lsof` and `docker
ps` show nothing on port 8088, there can be leftover Docker network artifacts,
iptables rules, or system-level blockers.
Here’s what you should try next:
1. Change the host port mapping for Superset in your Docker Compose file from
`8088:8088` to something else, like `8888:8088`, and try again. This rules out
hidden port conflicts or system-level issues. You only need to change the
`ports:` section for the `superset` service (not worker/beat), for example:
```yaml
ports:
- 8888:8088
```
Optionally, update `SUPERSET_PORT=8888` in `docker/.env` for consistency,
but this isn't required for the mapping to work
[source](https://github.com/apache/superset/discussions/34735#discussioncomment-14139549).
2. Prune unused Docker networks and volumes to clear out any leftovers:
```
docker network prune
docker volume prune
```
Then restart the Docker daemon.
3. Check for orphaned iptables rules or firewall settings that could block port
8088:
```
sudo iptables -L -n -v
```
4. Make sure Docker is running with sufficient privileges (not in rootless
mode), and if you’re on Linux, check for SELinux/AppArmor restrictions.
5. Check the Docker daemon logs (`journalctl -u docker` or `sudo tail -f
/var/log/docker.log`) for more details on the port binding failure.
The warnings you see (memory overcommit, hardlink fallback, "user already
exists", "Unknown Operation!!!") are not fatal and can be safely ignored for
this networking issue—they only affect performance or are benign log messages.
If you find any new errors or logs, share them and I can help interpret!
<!-- 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/f161d9ea-52d6-4517-a32e-6a1002353fe5?feedback_type=great_response)
|
[Irrelevant](https://app.dosu.dev/response-feedback/f161d9ea-52d6-4517-a32e-6a1002353fe5?feedback_type=irrelevant_answer)
|
[Incorrect](https://app.dosu.dev/response-feedback/f161d9ea-52d6-4517-a32e-6a1002353fe5?feedback_type=incorrect_sources)
|
[Verbose](https://app.dosu.dev/response-feedback/f161d9ea-52d6-4517-a32e-6a1002353fe5?feedback_type=too_verbose)
|
[Hallucination](https://app.dosu.dev/response-feedback/f161d9ea-52d6-4517-a32e-6a1002353fe5?feedback_type=hallucination)
| [Report
🐛](https://app.dosu.dev/response-feedback/f161d9ea-52d6-4517-a32e-6a1002353fe5?feedback_type=bug_report)
|
[Other](https://app.dosu.dev/response-feedback/f161d9ea-52d6-4517-a32e-6a1002353fe5?feedback_type=other)</sup>
[](https://app.dosu.dev/a28d3c7e-a9d3-459e-9fb6-3a6f9ff4f357/ask?utm_source=github) [](https://cursor.com/link/prompt?text=The%20docker-proxy%20error%20isn%27t%20caused%20by%20Superset%20or%20its%20configuration%E2%80%94it%27s%20almost%20always%20a%20host-level%20Docker%20networking%20issue.%20Even%20if%20%60lsof%60%20and%20%60docker%20ps%60%20show%20nothing%20on%20port%208088%2C%20there%20can%20be%20leftover%20Docker%20network%20artifacts%2C%20iptables%20rules%2C%20or%20system-level%20blockers.%0A%0AHere%E2%80%99s%20what%20you%20should%20try%20next%3A%0A%0A1.%20Change%20the%20host%20port%20mapping%20for%20Superset%20in%20your%20Docker%20Compose%20file%20from%20%608088%3A8088%60%20to%20something%20else%2C%20like%20%608888%3A8088%60%2C%20and%20try%20again.%20This%20rules%20out%20hidden%20port%20conflicts%20or%20system-level%20issues.%20You%20only%20need%20to%20change%20the
%20%60ports%3A%60%20section%20for%20the%20%60superset%60%20service%20%28not%20worker/beat%29%2C%20for%20example%3A%0A%20%20%20%60%60%60yaml%0A%20%20%20ports%3A%0A%20%20%20%20%20-%208888%3A8088%0A%20%20%20%60%60%60%0A%20%20%20Optionally%2C%20update%20%60SUPERSET_PORT%3D8888%60%20in%20%60docker/.env%60%20for%20consistency%2C%20but%20this%20isn%27t%20required%20for%20the%20mapping%20to%20work%20%5Bsource%5D%28https%3A//github.com/apache/superset/discussions/34735%23discussioncomment-14139549%29.%0A%0A2.%20Prune%20unused%20Docker%20networks%20and%20volumes%20to%20clear%20out%20any%20leftovers%3A%0A%20%20%20%60%60%60%0A%20%20%20docker%20network%20prune%0A%20%20%20docker%20volume%20prune%0A%20%20%20%60%60%60%0A%20%20%20Then%20restart%20the%20Docker%20daemon.%0A%0A3.%20Check%20for%20orphaned%20iptables%20rules%20or%20firewall%20settings%20that%20could%20block%20port%208088%3A%0A%20%20%20%60%60%60%0A%20%20%20sudo%20iptables%20-L%20-n%20-v%0A%20%20%20%60%60%60%0A%0A4.%20Make%20sure%20Docker%
20is%20running%20with%20sufficient%20privileges%20%28not%20in%20rootless%20mode%29%2C%20and%20if%20you%E2%80%99re%20on%20Linux%2C%20check%20for%20SELinux/AppArmor%20restrictions.%0A%0A5.%20Check%20the%20Docker%20daemon%20logs%20%28%60journalctl%20-u%20docker%60%20or%20%60sudo%20tail%20-f%20/var/log/docker.log%60%29%20for%20more%20details%20on%20the%20port%20binding%20failure.%0A%0AThe%20warnings%20you%20see%20%28memory%20overcommit%2C%20hardlink%20fallback%2C%20%22user%20already%20exists%22%2C%20%22Unknown%20Operation%21%21%21%22%29%20are%20not%20fatal%20and%20can%20be%20safely%20ignored%20for%20this%20networking%20issue%E2%80%94they%20only%20affect%20performance%20or%20are%20benign%20log%20messages.%0A%0AIf%20you%20find%20any%20new%20errors%20or%20logs%2C%20share%20them%20and%20I%20can%20help%20interpret%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-15686332
----
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]
