Can't connect to docker starting debug port 2375

EvetsMostel1 · July 7, 2026, 10:20pm

I upgraded docker from 28.5.2 to 29.6.1. I have the override to have docker listen on port 2375, and it is doing so shown in the status. However, it also has this showing in docker info:
[DEPRECATION NOTICE]: API is accessible on http://[::]:2375 without encryption.
Access to the remote API is equivalent to root access on the host. Refer
to the ‘Docker daemon attack surface’ section in the documentation for
more information: Docker Engine security | Docker Docs
In future versions this will be a hard failure preventing the daemon from starting! Learn more at: Protect the Docker daemon socket | Docker Docs

When I check the port, it is indeed closed:

Starting Nmap 7.94SVN ( https://nmap.org ) at 2026-07-07 14:43 PDT
Nmap scan report for 10.40.100.5
Host is up (0.0011s latency).

PORT STATE SERVICE
2375/tcp closed docker

Nmap done: 1 IP address (1 host up) scanned in 0.03 seconds

I noticed that I now have iptables entries and on the Chain Docker, it only has one entry of 172.17.0.2 tcp dpt:5000, but nothing about the 2375 port.
So it appears that I need to add that port to the IPTables. Is that the case?

Thanks,
Steve

ToradexAI · July 7, 2026, 10:21pm

Hi, I’m the Toradex AI Assistant.

I might make mistakes or occasionally get you wrong. Our support team will step in if needed.

Based on the sources provided, I don’t have specific documentation about configuring Docker to listen on port 2375 or managing iptables rules for this purpose on Torizon OS.

However, I can help you better if you provide some additional information about your setup:

Which Toradex hardware are you using? (e.g., Verdin i.MX8M Plus, Apalis i.MX8, Colibri iMX8X)
Which version of Torizon OS are you running?

You can get this information by running the tdx-info command on your device. More details about this command are available at: Getting Device Information with Tdx-Info | Toradex Developer Center

Regarding your specific issue with Docker port 2375:

The deprecation notice you’re seeing indicates that Docker is moving away from allowing unencrypted remote API access. The port showing as “closed” in your nmap scan suggests that while Docker may be configured to listen on that port, something (possibly iptables, firewall rules, or Docker’s own security restrictions) is blocking external access.

General guidance (not specific to Torizon without knowing your setup):

Docker’s newer versions are increasingly restrictive about exposing the daemon socket without TLS
iptables rules may indeed need adjustment, but this depends on your network configuration
The Torizon IDE Extension typically handles Docker communication differently and may not require port 2375 to be exposed

Could you clarify what you’re trying to achieve with port 2375? Are you:

Using the Torizon IDE Extension for development?
Trying to connect remotely to Docker on your Torizon device?
Following a specific workflow or tutorial?

Best regards,
Toradex AI Assistant.

Did you like my answer?

If I answered your question, please tick the “Solution” checkbox.

For follow-up questions to me, please use @ToradexAI in your post.

EvetsMostel1 · July 7, 2026, 10:32pm

Yes, I am using the Torizon extension, and it is complaining that it can’t connect to docker on port 2375. If there is a way around that, please let me know what it is.
If you look at the ticket, it has that I am on a Verdin imx8mplus with torizonOS, running 7.3.0.
Thanks,
Steve

ToradexAI · July 7, 2026, 10:32pm

Thank you for confirming your setup - Verdin iMX8M Plus with Torizon OS 7.3.0.

The issue you’re experiencing with Docker port 2375 and the Torizon IDE Extension is a known compatibility problem with Docker version 29(1).

Docker 29 Incompatibility

When using Docker v29 and attempting to start a debug session, you might encounter failures. The error in the terminal typically looks like issues connecting to the Docker daemon(1).

Solutions

Alternative Workaround: Downgrade Docker

If you are unable to use the Pre-Release version of the Torizon IDE Extension, you can resolve the incompatibility by downgrading your Docker installation to version 28.x(1).

Additional Troubleshooting

If the issue persists after trying the above solutions, there are a few other things to check:

Network Configuration: Ensure that port 2375 is accessible between your development PC and the Verdin board. In multi-NIC environments, the extension may have difficulty detecting the correct host IP(1)(2).
Host IP Override: If your PC has multiple network interfaces or uses VPN, you may need to set the torizon.overwriteHostIp setting in VS Code global settings to the correct IP address of your main interface(1).
Check Internal Logs: You can check the internal VS Code logs by opening the command palette and selecting Developer: Toggle Developer Tools, then clicking on the Console tab(1).

The primary issue appears to be the Docker 29 incompatibility, so updating the Torizon IDE Extension or downgrading Docker should resolve your problem.