Question: I'm pulling data using php dom parser and writing it to the table but I don't want all of this data to come in I want to add a limit How can I do it

```
 <?php $st = 0;foreach ($c as $item): ?>                       
    <tr>
      <td> <?php echo $saat = $item->find("time",0)-> plaintext;  ?> </td>
      <td> <?php echo $takim1 = $item->find("span.homespan",0)-> plaintext;  ?> </td>
      <td><?php echo $takim2 = $item->find("span.awayspan",0)-> plaintext;  ?> </td>
      <td> <?php echo $oran = $item->find(".tipdiv > span",0)-> plaintext;  ?> </td>
    </tr>
 <?php endforeach ?>           

```

Answer: 
`Listening to a single IP address` seems not correct. The service is listening **at** an IP address.

Let's say your VM has two network interfaces (ethernet cards):

Network 1 → subnet: `10.0.0.0/24` and IP `10.0.0.100`  

Network 2 → subnet: `10.0.1.0/24` and IP `10.0.1.200`

* If you set `127.0.0.1:80:80` that means that your service listening at `127.0.0.1`'s ([localhost](https://en.wikipedia.org/wiki/Localhost)) port 80.
* If you want to access service from `10.0.0.0/24` subnet you should set `10.0.0.100:80:80` and use `http://10.0.0.100:80` address to be able connect your container from external hosts

If you want to access service from multiple networks simultaneously you can bind the container port to multiple ports, where the IP is the [connection source IP](https://en.wikipedia.org/wiki/Computer_network)):

```
ports:
  - 10.0.0.100:80:80
  - 10.0.1.200:80:80
  - 127.0.0.1:80:80

```

And don't forget to open 80 port at VM's firewall, if a firewall exists and restricts that network
If you give Compose `ports:` (or `docker run -p`) an IP address, it must be a specific known IP address of a host interface, or `0.0.0.0` for "all interfaces". The Docker daemon gives this specific IP address to a [**bind**(2)](https://linux.die.net/man/2/bind) call, which takes an address and not a network, and follows the rules in [**ip**(7)](https://linux.die.net/man/7/ip) for IPv4.

With the output you show, you can only bind containers to `10.0.0.2`. If you want to use other IP addresses on the same network, you also need to assign them to the host; see for example [How can I (from CLI) assign multiple IP addresses to one interface?](https://askubuntu.com/questions/547289/how-can-i-from-cli-assign-multiple-ip-addresses-to-one-interface) on Ask Ubuntu, and then you can bind a container to the newly-added address.

If your system is on multiple physical networks, you can have any number of `ports:` so long as the host address and host port are unique. In particular you can have multiple `ports:` that all forward to the same container port.

```yaml
ports:
  # make this visible to the external load balancer on port 80
  - '192.168.17.2:80:3000'
  # also make this visible to the internal network also on port 80
  - '10.0.0.2:80:3000'
  # and the management network but on port 3000
  - '10.99.0.36:3000:3000'

```

Again, the host must already have these IP addresses in the `ifconfig` output.