安装seafile 13,日志报错,请帮忙看看什么问题

[root@wingray seafile]# docker logs seafile -f
*** Running /etc/my_init.d/01_create_data_links.sh…
*** Booting runit daemon…
*** Runit started as PID 11
*** Running /scripts/enterpoint.sh…
2026-04-04 03:29:45 Nginx ready
nginx: [warn] conflicting server name “” on 0.0.0.0:80, ignored
2026-04-04 03:29:45 This is an idle script (infinite loop) to keep container running.
nginx: [warn] conflicting server name “” on 0.0.0.0:80, ignored
[2026-04-04 03:29:45] Now running setup-seafile-mysql.py in auto mode.
Checking python on this machine …

verifying password of user root … done


This is your configuration

server name:            seafile
server ip/domain:       192.168.1.8

seafile data dir:       /opt/seafile/seafile-data
fileserver port:        8082

database:               create new
ccnet database:         ccnet_db
seafile database:       seafile_db
seahub database:        seahub_db
database user:          seafile

Generating seafile configuration …

done
Generating seahub configuration …


Now creating seafevents database tables …



Now creating ccnet database tables …



Now creating seafile database tables …



Now creating seahub database tables …


Error: Failed to prepare seahub avatars dir: [Errno 39] Directory not empty: ‘groups’
Traceback (most recent call last):
File “/scripts/start.py”, line 91, in
main()
File “/scripts/start.py”, line 56, in main
init_seafile_server()
File “/scripts/bootstrap.py”, line 86, in init_seafile_server
call(‘{} auto -n seafile’.format(setup_script), env=env)
File “/scripts/utils.py”, line 71, in call
return subprocess.check_call(*a, **kw)
^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^^
File “/usr/lib/python3.12/subprocess.py”, line 413, in check_call
raise CalledProcessError(retcode, cmd)
subprocess.CalledProcessError: Command ‘/opt/seafile/seafile-server-13.0.20/setup-seafile-mysql.sh auto -n seafile’ returned non-zero exit status 1.

这种情况一般不是 Seafile 13 本身有问题,而更像是首次初始化没有完成、之后又重复启动,或者挂载的数据卷里本来就残留了旧数据。尤其是全新安装但复用了旧的 /opt/seafile-data/opt/seafile-mysql 之类目录时,比较容易出现这种情况。

如果这是全新部署,建议最稳妥的处理方式就是停掉容器,先备份后清空相关数据目录,再重新初始化一次,不要在同一份半初始化的数据上反复重试。

如果不是全新安装,而是想保留原有数据,那就先去检查 seahub-data/avatars/groups 目录是不是已经有残留文件,再决定是只清理这个目录,还是整体回退后重建。

我是新装,我改变了默认的目录,看到这个问题以后我曾经docker compose down,然后把数据目录下的所有目录都删除过,然后再重新docker compose up -d部署,同样不行

seafile 数据目录和数据库数据目录都删除了吗?
我本地测试并没有出现这个问题,是否配置有误?参考官方文档再仔细检查一下吧。
https://cloud.seafile.com/wiki/publish/seafile-manual/hk5G/