RiCoder Container Loading and Setup Errors in Docker
1. Error loading containers in Docker
This section describes errors related to loading and starting RiCoder containers in Docker.
Case 1. RiCoder containers did not start in Docker
Solution for Windows OS
Start the containers manually in Docker Desktop:
- Open the Containers panel in Docker Desktop.
- In the Containers panel, in the Actions column, click Start (triangle icon) for the containers that are not running. When a container starts successfully, its status changes to running (square icon). Exception: the migrate-1 database container. It must be loaded (status Created or Exited) but may not be running.
- Restart the server. This is a mandatory condition for the containers to load successfully.
- Open Docker Desktop → the Containers panel → the container status should change to Started.
Delete the containers from Docker Desktop and repeat the RiCoder installation.
- Open the Containers panel in Docker Desktop.
- In the Containers panel, in the Actions column, click Stop → Delete for the RiCoder (chop) containers.
- Restart the server.
- Open Docker Desktop or make sure it is running.
- Start the RiCoder installation wizard and go through the dialog steps again.
Detailed diagnostics of the container status in the command line:
1. Open the command line.
2. Enter the docker ps command to list the running Docker containers and their key parameters.
3. The STATUS column shows the current state of the container.
Solution for Linux OS
RiCoder containers do not start, crash, do not see files, services do not come up, etc.
Check that Docker is running. Enter the command:
docker run hello-world1. Docker is not running: a message like "Cannot connect to the Docker daemon" appears. Docker is not started or there are no permissions to run Docker.
# Start the Docker daemon
sudo systemctl start docker
# Enable autostart so that Docker starts automatically at system startup
sudo systemctl enable docker
# Add the user to the docker group
sudo usermod -aG docker $USER
# Log out and log in again or restart the system
reboot2. Docker is running: a welcome message appears.
The cause of the failure when starting the containers is related to the RiCoder images or their configuration.
2.1 Check the status of the RiCoder containers:
docker ps -aIf the status is:
- Exited (1), Exited (127), etc.: the container crashed at startup,
- Created: created but not started,
- Restarting: trying to restart.
docker start <chop_container name>2.3. Restart the Docker daemon
sudo systemctl restart dockerCase 2. Docker cannot load containers due to lack of resources
The error occurs due to a lack of memory, CPU or disk space on the server.
Solution for Windows OS
- Check the resources allocated in Docker Desktop.
- Go to Settings → Resources.
- Increase the RAM/CPU limits or stop unnecessary containers that are not chop containers.
- Go to the Container panel.
- Restart the chop containers. Click Stop → Start for the corresponding containers.
- Restart the server if necessary.
Solution for Linux OS
1. Check the allocated system resources (RAM, CPU).
Run the command:
htopMake sure the system has enough free memory and CPU. Resource requirements for RiCoder.
2. If there are not enough resources, stop unnecessary containers (not related to RiCoder).
# View the list of all Docker containers
docker ps
# Stop unnecessary ones:
docker stop container_name
# Restart the RiCoder containers
docker restart <chop_container name> <chop_container name> <chop_container name>
# Restart Docker
sudo systemctl restart dockerCase 3. Network problems
Docker cannot load container dependencies because of a firewall or proxy block. To check the network settings, perform authentication in the Yandex Docker registry (Container Registry) using a service account.
Make sure the registry authorization key file is in the /CHOP_DEPLOY/ directory. If the file is missing from this folder, network diagnostics will be incorrect, and an error related to missing access rights to the Yandex repository will occur instead.
Diagnose network problems.
Solution for Windows OS
Docker cannot load containers because of a firewall or proxy block.
1. Make sure your computer can access the Yandex Docker registry. Open the command line.
2. Enter the command:
ping cr.yandexIf the ping fails → there is a problem with the internet connection or DNS.
3. Temporarily disable the firewall and antivirus. Sometimes the firewall blocks Docker. Open Control Panel → Windows Defender Firewall → Advanced settings.
4. Disable the firewall for the private and public networks.
5. Try to start Docker Desktop.
If Docker works, configure exceptions in the firewall for docker.exe.
6. Check which proxies are used in the system:
Open PowerShell and enter the command:
netsh winhttp show proxyIf a proxy is required, configure it in the ~/.docker/config.json file.
Solution for Linux OS
1. Check the connection to the Yandex registry. Enter the command:
docker pull cr.yandex/crp9t9tcd2mq4pdn52fm/ chop-deploy-eqgateway-1
# cr.yandex - Yandex registry address
# crp9t9tcd2mq4pdn52fm - project identifier ("id" in the authorization key json file.
# chop-deploy-eqgateway-1 - container image name2. If you get an error like no such host, Docker cannot find the Yandex registry host. There is a network or DNS problem.
level=info msg="Error logging in to endpoint, trying next endpoint" error="Get \"https://cr.yandex/v2/\": dial tcp: lookup cr.yandex: no such host"
Get "https://cr.yandex/v2/": dial tcp: lookup cr.yandex: no such host3. Check the connection to the Yandex repository. Run the command:
ping cr.yandex- DNS and network are working: you see replies, for example: 64 bytes from...
- DNS or internet problem: you see the replies ping: unknown host or 100% packet loss
4. Additionally check DNS. Enter the command:
nslookup cr.yandex.ruIf there is an error, the problem is in the network, DNS or proxy.
5. Check whether the firewall is blocking the connection. Ubuntu uses UFW (Uncomplicated Firewall) by default. Run the command to check the UFW status:
sudo ufw status6. Temporarily disable UFW for the test:
sudo ufw disable7. Try again:
docker pull hello-world- If it works, the firewall was blocking Docker.
- If not, the problem is not in the firewall.
8. After the check, turn UFW back on:
sudo ufw enable9. Allow Docker in the firewall:
sudo ufw allow out 443/tcp # HTTPS (for Docker Hub)
sudo ufw allow out 53 # DNSOther less common Docker errors related to the network connection are possible. See the official Docker documentation for details.
Case 4. Docker Desktop bug. GUI error
- Restart Docker Desktop.
- Update to the latest version.
2. Docker cannot connect to the RiCoder host
Docker cannot bind the container port to a specific IP address and port on the server where the RiCoder software is deployed.
Error text: Error response from daemon: ports are not available: exposing port TCP 192.168.1.4:2180 -> 127.0.0.1:0: listen tcp4 192.168.1.4:2180: can't bind on the specified endpoint
Cause of the error
The IP address of the server for installing RiCoder is specified incorrectly.
Solution
Solution for Windows OS
- Close the installation wizard.
- Start the installation wizard again and go through the dialog steps.
- Enter the correct server IP address.
How to find out the server IP address in the local network in Windows 10/11?
Via the command line:
1. Open the command line and enter the command:
ipconfig2. Find the line IPv4 Address (in the Ethernet or Wi-Fi section): this is the server IP address.
Via the network settings:
- Open Windows Settings → Network & Internet.
- Select Ethernet or Wi-Fi → Connection properties.
- Find the IPv4 address line: this is the server IP address.
Solution for Linux OS
1. Close the installation wizard.
2. Start the installation wizard again and go through the dialog steps.
./launcher_linux3. Enter the correct server IP address.
How to find out the server IP address in the local network in Linux?
1. Open the terminal and enter the command:
ip a2. Find the line with inet: this is the server IP address.
3. Docker cannot connect to the RiCoder port
Error text: Error response from daemon: failed to set up container networking: driver failed programming external connectivity on endpoint chop-eqgateway-1 (a215fcac0b259cd7f15e50939ce5456a62f6707a526204307847ac88a3133bd0): Bind for 0.0.0.0:8080 failed: port is already allocated
Causes of the error
Cause | Solution |
1. An incorrect port was entered. The port is occupied by another process. 2. Insufficient access rights. For example, when trying to bind a port below 10000. | 1. Close the installation wizard. 2. Start the installation wizard again and go through the dialog steps. 3. Enter a port number in the range from 10000 to 65535 that is not occupied by another process. |
How to find the process occupying the specified port in Windows?
1. Close the installation wizard.
2. Open PowerShell.
3. Check which process uses the port, for example 10101. Enter the command:
netstat -ano | findstr :10101
# 10101 - the port specified during RiCoder installation.4. Start the installation wizard again.
5. Go through the dialog steps and specify a free port in the range from 10000 to 65535.
How to check the server port statuses in Windows?
1. Open PowerShell.
2. Enter the command:
netstat -an3. Check the list of ports. Ports with the LISTENING status are occupied.
4. Select a free port that is not shown in the list or not used by another service for installing RiCoder. This guarantees that RiCoder starts successfully without conflicts.
How to find the process occupying the specified port in Linux?
1. Close the installation wizard.
2. Check which process uses the port, for example 10101.
sudo lsof -i :101013. Start the installation wizard again.
./launcher_linux4. Go through the dialog steps and specify a free port in the range from 10000 to 65535.
How to check the server port statuses in Linux?
1. Enter the command:
sudo ss -tulnp
# or
sudo netstat -tulnp2. Check the list of ports. Ports with the LISTENING status are occupied.
3. Select a free port that is not shown in the list or not used by another service for installing RiCoder. This guarantees that RiCoder starts successfully without conflicts.
4. Docker is not running
The installation wizard cannot install the RiCoder containers because Docker is not running.
Error text: unable to get image 'cr.yandex/crplu9iv3k90kbpg8iki/server-prod:2025-04-28-dd2b15c': error during connect: in the default daemon configuration on Windows, the docker client must be run with elevated privileges to connect: Get "http://%2F%2F.%2Fpipe%2Fdocker_engine/v1.49/images/cr.yandex/crplu9iv3k90kbpg8iki/server-prod:2025-04-28-dd2b15c/json": open //./pipe/docker_engine: The system cannot find the file specified.
Cause of the error
Docker Desktop is not running. Docker must be running during RiCoder installation and operation: this is a mandatory condition.
Solution for Windows OS
- Close the installation wizard.
- In the Windows notification area (lower right corner of the screen), find the Docker icon (white whale logo).
- If the icon is displayed, Docker is running.
- Start the installation wizard again and go through the dialog steps.
You can also check the Docker Engine status in the Docker Desktop interface. In the Docker Desktop menu (whale icon in the lower left corner of the screen), the status should be Engine running.
Solution for Linux OS
1. Close the installation wizard.
2. Start Docker with the command:
systemctl start docker3. Start the installation wizard again and go through the dialog steps.
./launcher_linuxHow to check the Docker status?
Run the command in the terminal:
sudo systemctl status docker- If the status is active (running), Docker is started and running.
- If the status is inactive (dead), Docker is stopped and needs to be started.
5. Update error while Docker and RiCoder are running
The installation wizard cannot install the RiCoder update correctly. A message appears that the port is occupied, while the following conditions are met:
- Docker is running;
- RiCoder is open in the browser and running.
Error text: Error response from daemon: ports are not available: exposing port TCP 192.168.1.16:2180 -> 127.0.0.1:0: listen tcp4 192.168.1.4:2180: can't bind on the specified endpoint
Cause of the error
An improvement of the update mechanism is under development. The next version of the installation wizard will include changes to fix this error.
Solution
Download the latest release of the installation wizard from the official website and try to perform the update again.
Last updated: 09/29/2025





No comments to display
No comments to display