I have been using this stack on portainer for ages:
services:
db:
image: mariadb:10.11
container_name: seafile-mysql
environment:
- MYSQL_ROOT_PASSWORD=<redacted> # Requested, set the root's password of MySQL service.
- MYSQL_LOG_CONSOLE=true
- MARIADB_AUTO_UPGRADE=1
volumes:
- /poolof6s/MainFS/SubMain/config2/seafile:/var/lib/mysql # Requested, specifies the path to MySQL data persistent store.
networks:
- seafile-net
memcached:
image: memcached:1.6.18
container_name: seafile-memcached
entrypoint: memcached -m 256
networks:
- seafile-net
seafile:
image: seafileltd/seafile-mc:latest
container_name: seafile
ports:
- "8088:80"
# - "443:443" # If https is enabled, cancel the comment.
volumes:
- /poolof6s/MainFS/SubMain/CustomerBackups/seafile:/shared # Requested, specifies the path to Seafile data persistent store.
environment:
- DB_HOST=db
- DB_ROOT_PASSWD=<redacted, does match> # Requested, the value should be root's password of MySQL service.
- TIME_ZONE=America/Toronto # Optional, default is UTC. Should be uncomment and set to your local time zone.
- SEAFILE_ADMIN_EMAIL=<redacted> # Specifies Seafile admin user, default is 'me@example.com'.
- SEAFILE_ADMIN_PASSWORD=<redacted> # Specifies Seafile admin password, default is 'asecret'.
- SEAFILE_SERVER_LETSENCRYPT=false # Whether to use https or not.
- SEAFILE_SERVER_HOSTNAME=none.none.com # Specifies your host name if https is enabled.
depends_on:
- db
- memcached
networks:
- seafile-net
networks:
seafile-net:
Here is the message I have been getting:
tarting seahub at port 8000 ...
Error:Seahub failed to start.
Please try to run "./seahub.sh start" again
Traceback (most recent call last):
File "/scripts/start.py", line 94, in <module>
main()
File "/scripts/start.py", line 80, in main
call('{} start'.format(get_script('seahub.sh')))
File "/scripts/utils.py", line 70, in call
return subprocess.check_call(*a, **kw)
File "/usr/lib/python3.10/subprocess.py", line 369, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command '/opt/seafile/seafile-server-11.0.13/seahub.sh start' returned non-zero exit status 1.
I get the following errors in the DB container:
2025-06-19 10:51:08 1352 [Warning] Aborted connection 1352 to db: 'seahub_db' user: 'seafile' host: '172.22.0.4' (Got an error reading communication packets)
2025-06-19 10:51:08 1354 [Warning] Aborted connection 1354 to db: 'seafile_db' user: 'seafile' host: '172.22.0.4' (Got an error reading communication packets)
2025-06-19 10:51:08 1355 [Warning] Aborted connection 1355 to db: 'seahub_db' user: 'seafile' host: '172.22.0.4' (Got an error reading communication packets)
2025-06-19 10:51:08 1382 [Warning] Aborted connection 1382 to db: 'seahub_db' user: 'seafile' host: '172.22.0.4' (Got an error reading communication packets)
2025-06-19 10:51:08 1383 [Warning] Aborted connection 1383 to db: 'seahub_db' user: 'seafile' host: '172.22.0.4' (Got an error reading communication packets)
Error grabbing logs: invalid character '\x00' in string literal
And it seems to have gotten progressively worse and worse. Every time I restarted my server, I used to need to start seafile again. Then it came to that I needed to re-create the stack. Then it came to me needing to re-pull the stack and pull the images. Now its not working even with that.
Any idea how I can get this working?