cat /proc/net/sockstat
result:
sockets: used 4807
TCP: inuse 2190 orphan 4 tw 42 alloc 4430 mem 2247
UDP: inuse 38 mem 81
UDPLITE: inuse 0
RAW: inuse 0
FRAG: inuse 0 memory 0
cat /proc/net/sockstat
result:
sockets: used 4807
TCP: inuse 2190 orphan 4 tw 42 alloc 4430 mem 2247
UDP: inuse 38 mem 81
UDPLITE: inuse 0
RAW: inuse 0
FRAG: inuse 0 memory 0
Maybe in the old version of the docker environment, when using Docker compose to start the container, you will encounter the following error: Error response from daemon: could not find an available, non-overlapping IPv4 address pool among the defaults to assign to the network This is actually this It is a symptom of running out of default-address-pools. In some environments, docker-compose will use the private network of Class B by default. The private IP of segment 172 has a range, from 172.16.0.0 to 172.31.255.255. That is to say, when we start a docker-compose Project, it will eat a private section of Class B, which is very heroic.
No chance to attend Laracon in the US? Be a little fan, come and see the speeches of these top program developers. Let's find out what's new in Laravel!!
No Comment
Post your comment