title: Docker compose cannot start service address already in use?
body: <p>For some reason <code>docker-compose</code> does not like the address <code>203.0.113.1</code> for the gogs container in the below configuration.  Note that in the below example I have Gogs running on <code>203.0.113.3</code> which works, but if I change that to <code>203.0.113.1</code> then the message: </p>
  
  <blockquote>
    <p>ERROR: for f1d322793d47_docker_gogs_1  Cannot start service gogs: Address already in use.</p>
  </blockquote>
  
  <p>I have checked to make sure no container using the ip address <code>203.0.113.1</code> is running so I'm curious whether <code>docker-compose</code> just disallows that address for some reason in general?</p>
  
  <pre><code>    version: '3'
      services:
        gogs-nginx:
          build: ./nginx
          ports:
          - "80:80"
          networks:
            mk1net:
              ipv4_address: 203.0.113.2
        gogs:
          image: gogs/gogs
          ports:
          - "3000:3000"
          volumes: 
            - gogs-data:/data
          depends_on:
            - gogs-nginx
          networks: 
            mk1net:
              ipv4_address: 203.0.113.3
      volumes:
        gogs-data:
           external: true
      networks:
        mk1net:
          ipam:
            config:
              - subnet: 203.0.113.0/24
  </code></pre>