Network error at boot. Running in a docker container

Good afternoon, I run sefile in the Docker container, after starting I can’t upload the file to the server, I get a network error.

docker-compose.yml

version: '2.0'
services:
  db:
    image: mariadb:10.1
    container_name: seafile-mysql
    environment:
      - MYSQL_ROOT_PASSWORD=my_db_password
      - MYSQL_LOG_CONSOLE=true
    volumes:
      - /cloud/database:/var/lib/mysql 
    networks:
      - seafile-net

  memcached:
    image: memcached:1.5.6
    container_name: seafile-memcached
    entrypoint: memcached -m 256
    networks:
      - seafile-net
          
  seafile:
    image: seafileltd/seafile-mc:latest
    container_name: seafile
    ports:
      - "80:80"
    volumes:
      - /cloud/volumes:/shared 
    environment:
      - DB_HOST=db
      - DB_ROOT_PASSWD=my_db_password
      - TIME_ZONE=Etc/UTC  
      - SEAFILE_ADMIN_EMAIL=my_email 
      - SEAFILE_ADMIN_PASSWORD=my_password
      - SEAFILE_SERVER_LETSENCRYPT=false  
      - SEAFILE_SERVER_HOSTNAME=docs. seafile. com 
    depends_on:
      - db
      - memcached
    networks:
      - seafile-net

networks:
  seafile-net:

seafile.conf

[fileserver]
port = 8082

[database]
type = mysql
host = db
port = 3306
user = seafile
password = 830ca1f1-220c-4a72-976a-16411030447a
db_name = seafile_db
connection_charset = utf8

ccnet.conf

[General]
SERVICE_URL = http://docs.seafile.com:8000

[Database]
ENGINE = mysql
HOST = db
PORT = 3306
USER = seafile
PASSWD = 830ca1f1-220c-4a72-976a-16411030447a
DB = ccnet_db
CONNECTION_CHARSET = utf8


[Client]
UNIX_SOCKET = /opt/seafile/ccnet.sock

Please tell me how to fix a network error?

Can you let us know what the exact error message is? Also, have you checked the log files, in particular, the ccnet log file?

ccnet.log
[05/17/20 20:11:12] …/common/session.c(148): using config file /opt/seafile/conf/ccnet.conf
[05/17/20 20:11:12] …/common/session.c(268): Update pubinfo file
[05/17/20 20:11:12] …/common/connect-mgr.c(515): Opened port 10001 to listen for incoming peer connections
[05/17/20 20:11:15] start to serve on pipe client
[05/17/20 20:11:41] start to serve on pipe client
[05/17/20 20:11:44] start to serve on pipe client
[05/17/20 20:11:58] start to serve on pipe client
[05/17/20 20:11:58] start to serve on pipe client
[05/17/20 20:11:58] start to serve on pipe client
[05/22/20 15:48:42] …/common/session.c(148): using config file /opt/seafile/conf/ccnet.conf
[05/22/20 15:48:42] …/common/session.c(268): Update pubinfo file
[05/22/20 15:48:42] …/common/connect-mgr.c(515): Opened port 10001 to listen for incoming peer connections
[05/22/20 15:48:42] socket file exists, delete it anyway
[05/22/20 15:48:46] start to serve on pipe client
[05/22/20 17:14:09] start to serve on pipe client
[05/22/20 17:14:21] start to serve on pipe client
[05/22/20 17:14:22] start to serve on pipe client
[05/22/20 17:14:27] start to serve on pipe client

I did not find any information in this logic by mistake, so I post the screenshot.
image

I’m not an expert on Docker, but if I can recall correctly, in order to get files to transfer over, you’ll have to “pass through” Docker’s port as well. I’m sorry, but I don’t know how to accomplish that as I’ve rarely used Docker. I’m hoping someone who is more well versed with Docker sees this and can help you. Everything looks good on your ccnet.log.