Closed hieunguyen8794 closed 1 year ago
Hi,
Could you please check your available RAM space and CPU when this happens.
Also make sure the format for the proxy given is correct in proxies.txt file
Please check the line number 301 in proxies.txt file and make sure it is in correct format.
In addition to this, you may also want to check the number of docker containers running by using the following command. By default you can run upto 1023 containers on a single network bridge.
Only tun2socks containers are to be considered here since the other containers go through this network. So you can run it with 1023 proxies on the host with all the apps.
sudo docker container ls -a | wc -l
Please note that the script is working as expected. There is no limit mentioned in the script. It depends on docker limitations and your available resources.
Thank you
Closing this since the script is working as expected. Please feel free to reach out for further queries. Thank you
Like I said, there are still plenty of resources. And I tried getting a proxy from 301 onwards to run on another computer and it still works normally.
@engageub Please try running at this number of proxies, I think you will encounter the same situation
It has already been tested with 1000 proxies earlier. Other users also have used about 1000 proxies. May I know which docker version you are using and how you are verifying the resources available. As mentioned the code does not have any limitation with respect to the number of containers.
Is 15% the available cpu or utilized cpu.
Can you run the following command and paste the output to see the limitation on your network. There are work arounds to overcome the limit by creating new network and using that network for containers.
sudo docker network inspect bridge
Here are some factors to consider when determining how many containers you can run on a single Docker bridge network:
IP Address Space: Docker's default bridge network uses a specific IP address range (usually 172.17.0.0/16 by default). The number of containers you can run on this network is limited by the available IP addresses within that range. Each container consumes one IP address.
Address Pool Size: The size of the address pool within the bridge network configuration can impact how many containers you can run. If the address pool is exhausted, you won't be able to create more containers on that network. You can adjust the address pool size in Docker's daemon configuration, as mentioned in a previous response.
System Resources: The physical or virtual resources of the host system, such as CPU, memory, and network bandwidth, can limit how many containers can run effectively. Running too many containers on a single host can lead to resource contention and performance degradation.
Container Resource Requirements: Each container has its own resource requirements, such as CPU and memory. The total resources available on the host should be sufficient to accommodate the combined requirements of all containers.
Network Throughput: The network throughput and bandwidth of the host can affect container communication and external network access. Running a large number of containers that generate a high network load may saturate the available bandwidth.
Container Interactions: Containers on the same bridge network can communicate with each other. If containers frequently interact and generate network traffic, it can impact the overall network performance.
Thank you
Hi, Please refer to this discussion also. https://github.com/engageub/InternetIncome/discussions/50#discussioncomment-7027048 Thank you
I got this error when running about 300 containers My computer has 2 cpu, 4gb ram configuration. And only running 3gb of ram when this error appeared. Is this an issue in the script?
docker: Error response from daemon: failed to create task for container: failed to create shim task: OCI runtime create failed: runc did not terminate successfully: exit status 2: unknown. Failed to start container for proxy. Exiting..