in progress_Errors Loading and Configuring RiCoder Containers in Docker

Start the containers manually in Docker Desktop:

1. Open the Containers panel in Docker Desktop.

2. In the Containers panel, under the Actions column, click Start (triangle icon) for any containers that are not running. Upon successful start, the container status changes to running (square icon).
Exception – the migrate-1 database container. It should be loaded – status Created or Exited, but it may not be running.

3. Restart the server. This is a mandatory condition for successfully loading the containers.

4. Open Docker Desktop -> Containers panel -> the container status should change to Started.

1. Open the Containers panel in Docker Desktop.

2. In the Containers panel, under the Actions column, click Stop -> Delete for the RiCoder containers (chop).

3. Restart the server.

4. Open Docker Desktop or ensure it is running.

5. Launch the RiCoder installation wizard and go through the dialog steps again.

Detailed container status diagnostics via command line:
1. Open the command prompt.
2. Enter the command docker ps – displays a list of running Docker containers and their key parameters.
3. The current container state is indicated in the STATUS column.

RiCoder containers are not starting, crashing, cannot see files, services are not coming up, etc.

Check that Docker is working by entering the command:

docker run hello-world

1. Docker is not working: A message appears saying "Cannot connect to the Docker daemon". Docker is not running or you do not have permission to run Docker.

# Start the Docker daemon
sudo systemctl start docker
# Enable autostart so Docker starts automatically on system boot
sudo systemctl enable docker
# Add the user to the docker group
sudo usermod -aG docker $USER
# Log out and log back in or reboo
reboot

2. Docker is working: A welcome message appeared.

The cause of the container startup failure is related to the RiCoder images or their configuration.

2.1 Check the status of RiCoder containers:

docker ps -a

If the status is:

• Exited (1), Exited (127) etc. — the container crashed upon startup,
• Created — created but not started,
• Restarting — attempting to restart

docker start <chop_container_name>

2.3 Restart the Docker daemon

sudo systemctl restart docker

1. Check the allocated resources in Docker Desktop.
2. Go to Settings -> Resources.
3. Increase the RAM/CPU limits or stop unnecessary containers that are not related to the chop containers.
4. Go to the Container panel.
5. Restart the chop containers. Click Stop -> Start for the corresponding containers.
6. Restart the server if necessary.

1. Check the allocated system resources (RAM, CPU).

   Run the command:

htop

Убедитесь, что у системы достаточно свободной памяти и CPU. Требования к ресурсам для RiCoder. 

2. Если ресурсов не хватает, остановите лишние контейнеры (не относящиеся к RiCoder).

# Посмотрите список всех контейнеров Docker
docker ps
# Остановите лишние:
docker stop имя_контейнера
# Перезапустите контейнеры RiCoder
docker restart <chop_имя контейнера> <chop_имя контейнера> <chop_имя контейнера>
# Перезапустите Docker
sudo systemctl restart docker

Docker cannot pull containers due to firewall or proxy blocking.

1. Ensure that your computer can access the Yandex Docker Registry. Open the Command Prompt.

2. Enter the command:

ping cr.yandex

1. If the ping fails → there is an issue with the internet connection or DNS.

2. Temporarily disable the firewall and antivirus. Sometimes the firewall blocks Docker. Open Control Panel → Windows Defender Firewall → Advanced settings.

3. Disable the firewall for both private and public networks.

4. Try launching Docker Desktop.
If Docker starts working, configure exceptions in the firewall for docker.exe.

5. Check what proxies are configured in the system:
Open PowerShell and enter the command:

netsh winhttp show proxy

If a proxy is required, configure it in the ~/.docker/config.json file.

1. Check the connection to the Yandex registry. Enter the command:

docker pull cr.yandex/crp9t9tcd2mq4pdn52fm/ chop-deploy-eqgateway-1
# cr.yandex - адрес реестра Яндекс
# crp9t9tcd2mq4pdn52fm - идентификатор проекта (“id” в json файле ключа авторизации.
# chop-deploy-eqgateway-1 - имя образа контейнера

2. If you receive an error like no such host - Docker cannot find the Yandex registry host. There is a network or DNS issue.

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 host

3. Check the connection to the Yandex repository. Run the command:

ping cr.yandex

• DNS и сеть работают - видите ответы, например: 64 bytes from...
• Проблема с DNS или интернетом - видите ответы ping: unknown host или 100% packet loss

4. Дополнительно проверьте DNS. Введите команду:

• DNS and network are working - you see replies, for example: 64 bytes from...
• DNS or internet issue - you see replies like ping: unknown host or 100% packet loss

4. Additionally check DNS. Enter the command:

nslookup cr.yandex.ru

If there is an error - the problem is with the network, DNS, or proxy.

5. Check if the firewall is blocking the connection. Ubuntu uses UFW (Uncomplicated Firewall) by default. Run the command to check UFW status:

sudo ufw status

6. Temporarily disable UFW for testing:

sudo ufw disable

7. Try again:

docker pull hello-world

• If it works — it means the firewall was blocking Docker.
• If not — the problem is not with the firewall.

8. Аfter testing, re-enable UFW:

sudo ufw enable

9. Allow Docker through the firewall:

sudo ufw allow out 443/tcp    # HTTPS (для Docker Hub)
sudo ufw allow out 53         # DNS

1. Close the installation wizard.

2. Launch the installation wizard again and proceed through the dialog steps.

3. Enter the correct server IP address.

Via the command line:

1. Open the Command Prompt and enter the command:

ipсonfig

2. Find the line with IPv4 Address (in the Ethernet or Wi-Fi section) – this is the server IP address.

Via network settings:

1. Open Windows Settings → Network & Internet.
2. Select Ethernet or Wi-Fi → Connection properties.
3. Find the IPv4 address line – this is the server IP address.

1. Close the installation wizard.

2. Launch the installation wizard again and proceed through the dialog steps.

./launcher_linux

3. Enter the correct server IP address.

1. Open the terminal and enter the command:

ip a

2. Find the line with inet – this is the server IP address.

1. Close the installation wizard.

2. Open PowerShell.

3. Check which process is using the port, for example, 10101. Enter the command:

netstat -ano | findstr :10101
# 10101 - порт, указанный при установке RiCoder.

4. Launch the installation wizard again.

5. Proceed through the dialog steps and specify a free port in the range of 10000 to 65535.

1. Open PowerShell.

2. Enter the command:

netstat -an

3. Check the list of ports. Ports with the status LISTENING are occupied.

4. Select a free port that does not appear in the list or is not used by another service for the RiCoder installation. This guarantees a successful launch of RiCoder without conflicts.

1. Close the installation wizard.

2. Check which process is using the port, for example, 10101:

sudo lsof -i :10101

3. Launch the installation wizard again

./launcher_linux

4. Proceed through the dialog steps and specify a free port in the range of 10000 to 65535.

1. Enter the command:

sudo ss -tulnp 
# или 
sudo netstat -tulnp

2. Check the list of ports. Ports with the status LISTEN are occupied.

3. Select a free port that does not appear in the list or is not used by another service for the RiCoder installation. This guarantees a successful launch of RiCoder without conflicts.

1. Close the installation wizard.
2. In the Windows notification area (bottom right corner of the screen), find the Docker icon (white whale logo).
3. If the icon is displayed – Docker is running.
4. Launch the installation wizard again and proceed through the dialog steps.

You can also check the Docker Engine status via the Docker Desktop interface. In the Docker Desktop menu (whale icon in the bottom left corner of the screen), the status should be – Engine running.

1. Close the installation wizard.

2. Check the Docker status:

systemctl start docker

3. If Docker is not running, start it

./launcher_linux

How to check Docker status?

Run the command in the terminal:

sudo systemctl status docker

• If the status is active (running) – Docker is up and running.
• If the status is inactive (dead) – Docker is stopped and needs to be started.