Creating the Docker Daemon Configuration File
You’re correct - if /etc/docker/daemon.json doesn’t exist on your Torizon OS system, you should create it from scratch (1). This is the standard location for Docker daemon configuration on Linux systems (1).
IPv6 vs IPv4 DNS Resolution Issue
Your analysis about DNS resolver differences is likely correct. Docker uses its own internal DNS resolution mechanism that can behave differently from system tools like curl (2). The issue you’re experiencing - where Docker repeatedly performs DNS queries but fails to establish connections - is characteristic of IPv6/IPv4 dual-stack resolution problems (2).
Why IPv6 Might Be Problematic
The key difference between your Windows Docker setup and Torizon OS could be:
- Different Docker versions - Your Windows system uses Docker 27.2.0 while Torizon OS 7.1.0 uses Docker 25.0.3
- Network stack differences - Windows and Linux handle IPv6 fallback mechanisms differently
- DNS resolution timing - Docker’s internal resolver might be timing out on IPv6 before falling back to IPv4
Recommended Configuration
Create /etc/docker/daemon.json with this configuration (1):
{
"ipv6": false,
"dns": ["8.8.8.8", "8.8.4.4"]
}
Then restart Docker:
sudo systemctl restart docker
Alternative Troubleshooting
If you prefer not to disable IPv6 entirely, you can also try:
- Test with explicit IPv4 DNS servers in the daemon configuration
- Check if your router/network has IPv6 routing issues specific to Docker’s connection patterns
- Monitor network traffic during Docker operations to see if IPv6 connections are being attempted and timing out
The fact that curl -6 fails while curl -4 works confirms that your network environment has IPv6 connectivity issues, even though IPv6 DNS resolution works (2). Docker’s behavior of repeatedly querying DNS without making HTTP connections suggests it’s getting stuck in the IPv6 resolution/connection phase.
Best regards, Toradex AI Assistant.
If I answered your question, please tick the “Solution” checkbox.
For follow-up questions to me, please use @ToradexAI in your post.