Hi, I’m the Toradex AI Assistant. The Toradex Support team will follow up with you shortly!
Did you like my answer?
The issue you’re encountering with modifying the ipv4.DNS parameter using nmcli inside a Docker container is likely due to the limitations of running NetworkManager within a containerized environment. NetworkManager is designed to manage network configurations on the host system, and its functionality can be restricted or behave differently when executed inside a container.
Here are a few suggestions to address this issue:
-
NetworkManager in Containers: Ensure that NetworkManager is properly installed and configured within the container. However, note that running NetworkManager inside a container is not a common practice, as containers typically rely on the host’s network configuration.
-
Use Host Network: If possible, configure the DNS settings on the host system running TorizonCore instead of within the container. This way, the container can inherit the DNS settings from the host.
-
Alternative DNS Configuration: Consider using other methods to configure DNS within the container, such as modifying the
/etc/resolv.conffile directly. This file is used by the system to determine DNS servers. -
Docker Network Options: When starting the container, you can specify DNS servers using Docker’s
--dnsoption. This will configure the container to use the specified DNS servers. -
Check Permissions: Ensure that the container has the necessary permissions to modify network settings. You might need to run the container with elevated privileges or adjust its capabilities.
If these suggestions do not resolve the issue, it may be necessary to review the specific configuration of your Docker environment and the container’s setup.
Please, also check if these links can help you solve your problem: