GitHub user dosubot[bot] added a comment to the discussion: docker installation
from github fails
<!-- Answer -->
The docker-proxy error is a Docker daemon issue, not a container or Superset
issue. Since you've switched to nftables, try disabling the userland proxy
entirely—this forces Docker to use kernel-level networking (via nftables)
instead of the docker-proxy process.
Add this to `/etc/docker/daemon.json`:
```json
{
"userland-proxy": false
}
```
Then restart Docker:
```bash
sudo systemctl restart docker
```
This should bypass the docker-proxy failure completely since Docker will route
traffic through nftables directly.
If that doesn't work, a few other things to check:
- Make sure you're on Docker 20.10+ (better nftables support)
- Check Docker logs for more details: `journalctl -u docker.service`
- As a last resort, you can try host networking mode by adding `network_mode:
"host"` to the superset service in your compose file (this bypasses Docker
networking entirely, but changes how you access the service)
This is a known Docker infrastructure issue rather than anything specific to
Superset—the project has no documented issues with docker-proxy failures.
<!-- 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/3e6e0fcb-44b2-44cc-a26e-37bcc1b8167a?feedback_type=great_response)
|
[Irrelevant](https://app.dosu.dev/response-feedback/3e6e0fcb-44b2-44cc-a26e-37bcc1b8167a?feedback_type=irrelevant_answer)
|
[Incorrect](https://app.dosu.dev/response-feedback/3e6e0fcb-44b2-44cc-a26e-37bcc1b8167a?feedback_type=incorrect_sources)
|
[Verbose](https://app.dosu.dev/response-feedback/3e6e0fcb-44b2-44cc-a26e-37bcc1b8167a?feedback_type=too_verbose)
|
[Hallucination](https://app.dosu.dev/response-feedback/3e6e0fcb-44b2-44cc-a26e-37bcc1b8167a?feedback_type=hallucination)
| [Report
🐛](https://app.dosu.dev/response-feedback/3e6e0fcb-44b2-44cc-a26e-37bcc1b8167a?feedback_type=bug_report)
|
[Other](https://app.dosu.dev/response-feedback/3e6e0fcb-44b2-44cc-a26e-37bcc1b8167a?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%20is%20a%20Docker%20daemon%20issue%2C%20not%20a%20container%20or%20Superset%20issue.%20Since%20you%27ve%20switched%20to%20nftables%2C%20try%20disabling%20the%20userland%20proxy%20entirely%E2%80%94this%20forces%20Docker%20to%20use%20kernel-level%20networking%20%28via%20nftables%29%20instead%20of%20the%20docker-proxy%20process.%0A%0AAdd%20this%20to%20%60/etc/docker/daemon.json%60%3A%0A%60%60%60json%0A%7B%0A%20%20%22userland-proxy%22%3A%20false%0A%7D%0A%60%60%60%0A%0AThen%20restart%20Docker%3A%0A%60%60%60bash%0Asudo%20systemctl%20restart%20docker%0A%60%60%60%0A%0AThis%20should%20bypass%20the%20docker-proxy%20failure%20completely%20since%20Docker%20will%20route%20traffic%20through%20nftables%20directly.%0A%0AIf%20that%20doesn%27
t%20work%2C%20a%20few%20other%20things%20to%20check%3A%0A-%20Make%20sure%20you%27re%20on%20Docker%2020.10%2B%20%28better%20nftables%20support%29%0A-%20Check%20Docker%20logs%20for%20more%20details%3A%20%60journalctl%20-u%20docker.service%60%0A-%20As%20a%20last%20resort%2C%20you%20can%20try%20host%20networking%20mode%20by%20adding%20%60network_mode%3A%20%22host%22%60%20to%20the%20superset%20service%20in%20your%20compose%20file%20%28this%20bypasses%20Docker%20networking%20entirely%2C%20but%20changes%20how%20you%20access%20the%20service%29%0A%0AThis%20is%20a%20known%20Docker%20infrastructure%20issue%20rather%20than%20anything%20specific%20to%20Superset%E2%80%94the%20project%20has%20no%20documented%20issues%20with%20docker-proxy%20failures.) [](https://go.dosu.dev/discord-bot) [](https://twitter.com/intent/tweet?text=%40dosu_ai%20
helped%20me%20solve%20this%20issue!&url=https%3A//github.com/apache/superset/discussions/37610)
GitHub link:
https://github.com/apache/superset/discussions/37610#discussioncomment-15824924
----
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]
