Duplicate
Details
Assignee
MuhammadMuhammadReporter
Ramond QueenRamond QueenLabels
Components
Fix versions
Affects versions
Priority
Low
Details
Details
Assignee
Muhammad
MuhammadReporter
Ramond Queen
Ramond QueenLabels
Components
Fix versions
Affects versions
Priority
More fields
More fields
More fields
Katalon Platform
Katalon Platform
Katalon Platform
Created March 11, 2025 at 5:30 AM
Updated March 13, 2025 at 4:38 PM
Resolved March 13, 2025 at 4:37 PM
Some users in certain regions are experiencing network connectivity issues when executing Docker pull operations, often needing to set up proxies as a workaround. After migrating from Kubernetes to Docker on TrueNAS Scale, the HTTP Proxy settings configured under Network —> Global Configuration no longer apply to Docker.
My current solution involves manually configuring the Docker proxy by creating a file using the command
sudo nano /etc/systemd/system/docker.service.d/http-proxy.conf
and adding the following content:To apply these changes, the daemon and Docker need to be restarted:
The drawback of this approach is that the settings reset after a TrueNAS restart, requiring manual reconfiguration. I would like to request this process to be automated and integrated into the middleware.