Containers network error when use docker with live-restore

This is my docker-compose file

version: '3'

services:
  nginx-proxy:
    image: jwilder/nginx-proxy
    container_name: nginx-proxy
    ports:
      - "80:80"
    volumes:
      - /var/run/docker.sock:/tmp/docker.sock:ro

  mysql:
    image: mariadb
    ports: 
      - 3307:3306
    environment:
      MYSQL_ROOT_PASSWORD: example

  wordpress:
    image: wordpress
    ports:
      - 8081:80
    environment:
      WORDPRESS_DB_PASSWORD: example
      VIRTUAL_HOST: domain.com
    depends_on:
      - mysql
      - nginx-proxy

My daemon.json file:

  • Updating WordPress inside a contaner. No FTP access
  • Get IP address of Docker with Ansible
  • Is there a way to avoid pushing node_modules on every push using Docker?
  • Cronjob in symfony running on docker
  • Python in docker container
  • How to configure Docker mysql + aspnet
  • {
    "live-restore": true
    }
    

    Everything work fine when docker daemon on but when i turn it off with service docker stop , my wordpress site cant connect to database , it seem that there is something wrong with their internal network because i still can access database from outsite , please help me fix this .

  • Private docker registry and high availability
  • Vagrant and Docker not playing nice
  • Why does docker-compose build not reflect my django code changes?
  • Logging from one Docker Container to Another
  • Docker not starting with docker start command in 1.3
  • Removing docker image errors “No such id” with a different image ID
  • Docker will be the best open platform for developers and sysadmins to build, ship, and run distributed applications.