Skip to main content

No Connection Between Docker and the RiCoder Host

Docker cannot connect to the RiCoder host because of incorrect network settings.

Cause

Docker Desktop automatically configures its internal network and assigns IP addresses to containers. Changing these settings manually is not recommended: it can lead to connection errors. If the settings were changed manually, restore the original configuration.

Solution for Windows OS

Specify the default host IP address in the Docker Desktop settings.

  1. Open Docker Desktop.
  2. Go to the Settings → Resources → Network menu.
  3. Enter the host IP address suggested by default.
  4. Click Apply & Restart to save and restart Docker.
Solution for Ubuntu OS

When Docker network settings are changed manually or conflict with external networks (for example, VPN or the local network), an error connecting to containers or the host may occur. These are errors such as:

  • Containers cannot connect to the internet.
  • The host cannot access a service in a container.
  • Errors like: Cannot connect to container, Connection refused, No route to host.

The settings are made through configuration files and the command line.

Other possible reasons for changed network settings:

  • The daemon.json file was changed manually: an incorrect IP range was set that conflicts with the local network.
  • Docker Engine was not restarted after the settings were changed.
  • Incorrect DNS settings in /etc/docker/daemon.json or /etc/resolv.conf.

Manual changes can lead to connection errors between the host and containers. To restore operation, check daemon.json and /etc/hosts, restart Docker and make sure there are no IP conflicts.


Last updated: 11/13/2025